Repository navigation
ci: fix msan timeouts in CI - #2687
Merged
Merged
Conversation
msan lacked a -timeout flag, falling back to go test's default 10-minute per-package timeout. Memory sanitizer instrumentation is slow enough to exceed that regularly, causing spurious CI failures.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
-timeoutflag, so go test fell back to its default 10-minute per-package timeout-O0 -fsanitize=memory) is slow enough to regularly exceed that, causing spurious CI failures-timeout 60mfor msan and-timeout 30mfor asan, matching the pattern already used in docker.yaml and tests.yaml