-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 failure: AggregateException: Not all processes in process tree could be terminated. #93321
Comments
Tagging subscribers to this area: @dotnet/area-system-diagnostics-process Issue DetailsFailed in: runtime-coreclr jitstress 20231009.2 Failed tests:
Error message:
Stack trace:
More failures
|
Failed in: runtime-coreclr r2r-extra 20240224.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr r2r-extra 20240316.1 Failed tests:
Error message:
Stack trace:
|
@mangod9, what is the status of this failure? |
seems to be only affecting jitstress. Did you notice this failure on a PR run? |
Failed in: runtime-coreclr r2r-extra 20240323.1 Failed tests:
Error message:
Stack trace:
|
This is hit intermittently on both macOS and Linux, different architectures, for different tests. I have just resolved #99885 as a duplicate. The problem seems to be a race condition in the implementation of The processes in the tree can be starting and exiting while |
Failed in: runtime-coreclr r2r 20240401.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr r2r-extra 20240407.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr r2r-extra 20240413.1 Failed tests:
Error message:
Stack trace:
|
cc @dotnet/area-system-diagnostics-process |
Failed in: runtime-coreclr r2r 20240415.2 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr r2r 20240416.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr r2r 20240417.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr r2r 20240419.1 Failed tests:
Error message:
Stack trace:
|
@jeffhandley, what is the status of this test failure? |
@jkotas would it be OK to ignore "operation not permitted" errors on |
@mikelle-rogers we currently don't have a fix nor a consistent repro, we could spend more time looking into it but not sure if we could get a repro at all. |
I do not know. We need to understand what leads to the "operation not permitted" errors. |
Delete workaround added in #102958 once this gets fixed. |
Failed in: runtime-coreclr jitstress 20231009.2
Failed tests:
Error message:
Stack trace:
More failures
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎⚠️ Provided build not found. Provide a valid build in the "Build: 🔎" line.
Result validation:
Validation performed at: 4/2/2024 6:55:27 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: