Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timeout on jhack tail (integration_test_charm.yaml) #223

Closed
carlcsaposs-canonical opened this issue Aug 7, 2024 · 5 comments · Fixed by #224
Closed

Timeout on jhack tail (integration_test_charm.yaml) #223

carlcsaposs-canonical opened this issue Aug 7, 2024 · 5 comments · Fixed by #224
Labels
bug Something isn't working

Comments

@carlcsaposs-canonical
Copy link
Contributor

carlcsaposs-canonical commented Aug 7, 2024

jhack tail takes longer than 3 minutes when debug log is large
e.g. https://github.com/canonical/mongodb-operator/actions/runs/10276480008/job/28437246655#step:33:1

not exactly sure what's the root cause, it appears to be related to log size but not only that

the previously linked run has 74.8 MB debug log

this run has two models each with a 4.0 MB log: https://github.com/canonical/postgresql-operator/actions/runs/10276476581/job/28437198646 (jhack tail takes 1:19)

this run has a 13.6 MB log: https://github.com/canonical/mongodb-operator/actions/runs/10276480008/job/28437244101#step:33:7 (jhack tail takes >3 min)

reported by @taurus-forever

@carlcsaposs-canonical carlcsaposs-canonical added the bug Something isn't working label Aug 7, 2024
Copy link

github-actions bot commented Aug 7, 2024

@carlcsaposs-canonical
Copy link
Contributor Author

contacted Pietro to see if there's maybe a quick optimization on jhack

otherwise will remove from integration_test_charm.yaml (sorry @paulomach)

@taurus-forever
Copy link

Thank you @carlcsaposs-canonical , we can report it officially to jhack repo if necessary. cc: @PietroPasotti

@carlcsaposs-canonical
Copy link
Contributor Author

testing without our python "tee" wrapper here: https://github.com/canonical/mongodb-operator/actions/runs/10286598261?pr=452
and testing with --output per Pietro's suggestion here: https://github.com/canonical/mongodb-operator/actions/runs/10286611587?pr=452

@carlcsaposs-canonical
Copy link
Contributor Author

opening and reclosing issue to test jira sync

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants