-
-
Notifications
You must be signed in to change notification settings - Fork 2k
fix(ci): Make integration tests on Linux arm64 not flaky #4313
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
Draft
aldy505
wants to merge
12
commits into
aldy505/feat/bump-seaweedfs-425
Choose a base branch
from
aldy505/fix/ci-arm64-flakes
base: aldy505/feat/bump-seaweedfs-425
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+59
−43
Draft
Changes from 6 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
53481c9
fix: add more things to inspect failures
aldy505 7abcbcd
fix(ci): declare timeout minutes
aldy505 3cf271a
feat: longer kafka socket timeout duration
aldy505 ebf1246
feat: tune kafka to be more lenient
aldy505 2b8fa2b
Merge branch 'master' into aldy505/fix/ci-arm64-flakes
aldy505 1007e6b
Merge branch 'master' into aldy505/fix/ci-arm64-flakes
aldy505 f9ce3cc
chore: increase kafka request timeout to 60s
aldy505 4064d5f
fix: use --max-poll-interval-ms flag
aldy505 8b51512
fix: remove --max-poll-interval-ms on snuba subscriptions consumers
aldy505 e5fdf1f
Merge branch 'master' into aldy505/fix/ci-arm64-flakes
aldy505 59c6231
feat: healthcheck & adjust max-poll-interval for snuba-replacer
aldy505 4ced5b8
Merge branch 'aldy505/feat/bump-seaweedfs-425' into aldy505/fix/ci-ar…
aldy505 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From logs:
searching "Consumer group session timed out" shows a couple more kafka timeouts after 30s as well, maybe we should increase kafka timeout even further?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aminvakil holy sh*t you're right
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be honest, I didn't catch this myself, it's been a while since I also use AI to review stuff :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But the problem persist. I have no idea other to blame github's arm64 runners.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, they are too slow, this happens to me as well in other projects.
I searched "Consumer group session timed out" in latest run:
Seems like they still have 30 seconds timeout.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is according to AI:
Root cause summary:
session.timeout.ms and heartbeat.interval.ms are silently discarded.
session.timeout.ms is force-set to 30s — which is exactly what the ~31.7s timeout error reflects.
Recommended fix (no code change required): Pass --max-poll-interval-ms 300000 (or any value ≥ 45000) to the sentry run consumer process-spans command in the self-hosted docker-compose.yml. This disables the HACK and allows the session timeout to stay at the safe default of
45s.
Let me try to mess things up again
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like it wasn't fixed, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It wasn't. But the first try works. I wonder if it's the cache, but I could be wrong