-
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
System.IO.Tests work item failing with SIGKILL #65791
Comments
Tagging subscribers to this area: @dotnet/area-system-io Issue DetailsRunfo Creating Tracking Issue (data being generated)
|
Looks like OOM (I do not see any coredumps captured):
|
My understanding when I looked at this before is that it is not possible to configure Linux to capture a core dump before oom-killing. So next step is probably to run locally, and even if it does not OOM, hopefully it is clear there is excessive memory use and then bisect. |
@dotnet/area-system-io Could someone take a look at this please? It's hitting PRs somewhat often |
Should System.IO.Tests be disabled, while being investigated? It is still happening quite often on rolling builds. |
@jeffhandley is anyone on the IO crew available to look at this? We can't disable all the IO tests en masse, if they can at least narrow down where hte memory usage is, or add some logging ,etc that would be a win. |
Too bad each test could not run in separate processes so that way the testing lib could just analyzer the working sets on them all to find the test that uses the most memory. |
@jozkee Could you take a look at this within the next couple days please? |
Runfo Tracking Issue: System.IO.Tests work item failing with SIGKILL
Displaying 100 of 118 results
Build Result Summary
The text was updated successfully, but these errors were encountered: