-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
System.Runtime.Tests Outerloop "killed" on Debian.10 and Debian.11 #58616
Comments
Tagging subscribers to this area: @dotnet/area-system-runtime Issue DetailsPR #58129 hit 4 times this failure:
Seems related to #56567 Not sure how to query Kusto to see all these failures. I bet they will be fairly common ...
|
Failing again in this build, the log:
|
We are missing a way to get a dump when we are killed for using too much memory. #56165 is similar but for IO tests. |
Hit in #66387.
|
Ideally we'd have a way to get some kind of diagnostics on OOM - as there's never a dump. Eg xunit could log the test name if memory is above a threshold, as it does for long running tests. |
PR #58129 hit 4 times this failure:
Seems related to #56567
Not sure how to query Kusto to see all these failures. I bet they will be fairly common ...
The text was updated successfully, but these errors were encountered: