Conversation
"racket-test/tests/future/fsema-lock.rkt" has drifted into the timeout. Its median duration was 64.9s over pushes 73464-73505, 84.0s over 73506-73726, and 89.7s over 73735-73747 -- against a 90s limit. It now times out on 54% of pushes, up from 2%. 180s leaves room for that drift and for the variation in machine load that pushed it over in the first place. Note this does not help "gui-test/framework/tests/pasteboard.rkt", which does not time out because it is slow: across 348 runs it finishes in under 10s eight times and around 35s another 314 times, with nothing at all between 45s and 89s and 26 runs killed at the limit. That is a hang, and a longer limit only makes it take longer to report.
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
1 participant
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.
"racket-test/tests/future/fsema-lock.rkt" has drifted into the timeout.
Its median duration was 64.9s over pushes 73464-73505, 84.0s over
73506-73726, and 89.7s over 73735-73747 -- against a 90s limit. It now
times out on 54% of pushes, up from 2%.
180s leaves room for that drift and for the variation in machine load
that pushed it over in the first place.
Note this does not help "gui-test/framework/tests/pasteboard.rkt", which
does not time out because it is slow: across 348 runs it finishes in
under 10s eight times and around 35s another 314 times, with nothing at
all between 45s and 89s and 26 runs killed at the limit. That is a hang,
and a longer limit only makes it take longer to report.