-
Notifications
You must be signed in to change notification settings - Fork 23
Fixes skupperproject#1750: Added asan and tsan to the new arm64 runner #1749
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
Merged
ganeshmurthy
merged 4 commits into
skupperproject:main
from
ganeshmurthy:GITHUB-ARM-ASAN-2
Mar 10, 2025
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
8fb24ad
Fixes #1750: Added asan and tsan to the new arm64 runner
ganeshmurthy ed7e598
Code review change - Added comment and modified test name in order to…
ganeshmurthy 1620df9
Code review fix. Set self.delay_count=2
ganeshmurthy 25c1e77
Set flow_count to 25 from 100
ganeshmurthy 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.
Is there a reason these are removed? The problem is if these addresses are not flushed out before the next test runs then they interfere with the test and things get flakey
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.
The test was waiting on the
_wait_address_gone()
and looping inside that function and ultimately timed out. I removed it becausetest_13_streaming_balanced_parallel()
was the last test in the test suite (StreamingMessageTest
). I understand that removing this code would be a problem if we ever add atest_14
but this test annoyingly keeps failing intermittently in aarch64. I could put it back if you feel strongly about it.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 makes sense, but it leaves a time bomb for some poor unsuspecting dev like myself when I forget that test_13_xxx must be last. Would you be ok with changing the test number to some obvious indication that it must be last and drop a comment? I know I've used the prefix test_9999_xxx in those other test cases were a test needed to be run last in a test case (see tcp adaptor tests for an example)