-
Notifications
You must be signed in to change notification settings - Fork 5k
CI flakiness: mono interpreter build getting killed #114123
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
Comments
Tagging subscribers to this area: @akoeplinger, @matouskozak |
fyi: @BrzVlad |
We use mono interpreter to run msbuild, right ? This is building 3 groups of many small tests That combined with WASM toolchain memory demands makes msbuild run out of memory (docker kills it). As far as I can tell, it never passes for WASM and it's killed in the group 2 already.
|
I disabled part of the test on browser, because 100% fail rate was not helping anybody. This is |
Uh oh!
There was an error while loading. Please reload this page.
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=998900&view=logs&j=3e93a48f-6568-53f2-76b3-1285c183c39d
Build error leg or test failing: Build / browser-wasm linux Release AllSubsets_Mono_RuntimeTests monointerpreter / Build Tests
Pull request: #114058
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=998900
Error message validated:
[RuntimeVariant=monointerpreter*exited with code 137.
]Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 4/1/2025 9:14:37 PM UTC
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=998900
Error message validated:
[RuntimeVariant=monointerpreter.*exited with code 137
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 4/1/2025 9:15:42 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: