-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Test failures: GCStress time out in tracing pauseonstart, reverse tests #38524
Comments
Dotnet-GitSync-Bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Jun 28, 2020
BruceForstall
added a commit
to BruceForstall/runtime
that referenced
this issue
Jun 28, 2020
PR to disable for GCStress: #38525 |
BruceForstall
added a commit
that referenced
this issue
Jun 29, 2020
Thanks @BruceForstall! PR should be out later today! |
Actually this should be fixed by #38474 which removes the internal timeouts in favor of letting Helix timeout if something goes wrong. |
kevinwkt
pushed a commit
to kevinwkt/runtimelab
that referenced
this issue
Jul 15, 2020
ghost
locked as resolved and limited conversation to collaborators
Dec 8, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
tracing\eventpipe\pauseonstart\pauseonstart\pauseonstart.cmd and tracing\eventpipe\reverse\reverse\reverse.cmd in various GCStress modes, such as
(there may be more)
with time outs, e.g.:
These stress modes significantly slow down the process, so it is not surprising that a short 5 seconds timeout is not sufficient.
The timeouts should be significantly increased. Or perhaps these should not be run under GCStress.
The text was updated successfully, but these errors were encountered: