-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[browser] System.Buffers.ArrayPool.Tests.ArrayPoolUnitTests
fails with out of memory
#101436
Comments
Tagging subscribers to 'arch-wasm': @lewing |
Tagging subscribers to this area: @dotnet/area-system-buffers |
The pattern is too broad and it is catching failures in System.Text.Json not ArrayPool tests. I'm going to close the issue, feel free to update the pattern to match the ArrayPool tests |
Updating the condition and reopening |
@kg here are some common arraypool failures |
Also worth reading #853 |
This is great log
I guess other places don't produce as nice message when they can't allocate |
no hits anymore |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=653237
Build error leg or test failing: System.Buffers.ArrayPool.Tests.ArrayPoolUnitTests.RentingSpecificLengthsYieldsExpectedLengths
Pull request: #101390
Error Message
Fill the error message using step by step known issues guidance.
Observed on
'WasmTestOnChrome-System.Buffers.Tests
log
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=653237
Error message validated:
[[FAIL] System.Buffers.ArrayPool System.OutOfMemoryException : Out of memory
]Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 4/25/2024 7:55:51 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: