Open ilonatommy opened 4 months ago
Tagging subscribers to 'arch-wasm': @lewing See info in area-owners.md if you want to be subscribed.
Tagging subscribers to this area: @dotnet/area-system-buffers See info in area-owners.md if you want to be subscribed.
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 https://github.com/dotnet/runtime/issues/853
This is great log
[11:40:08] info: System.Buffers.ArrayPool.Tests.CollectionTests 0 ms
[11:40:08] fail: [0x012251a0-dpty 11:40:08.951] [MONO] Could not allocate 131072 (1 * 131072) bytes
Error
at tu (http://127.0.0.1:40487/_framework/dotnet.runtime.js:3:199931)
at wasm_trace_logger (http://127.0.0.1:40487/_framework/dotnet.native.wasm:wasm-function[197]:0x155ad)
at eglib_log_adapter (http://127.0.0.1:40487/_framework/dotnet.native.wasm:wasm-function[697]:0x4e9fc)
at monoeg_g_logv_nofree (http://127.0.0.1:40487/_framework/dotnet.native.wasm:wasm-function[615]:0x4c119)
at monoeg_g_log (http://127.0.0.1:40487/_framework/dotnet.native.wasm:wasm-function[617]:0x4c1dc)
at monoeg_g_calloc (http://127.0.0.1:40487/_framework/dotnet.native.wasm:wasm-function[607]:0x4bf7c)
at monoeg_malloc0 (http://127.0.0.1:40487/_framework/dotnet.native.wasm:wasm-function[608]:0x4bf96)
at rehash_table (http://127.0.0.1:40487/_framework/dotnet.native.wasm:wasm-function[2198]:0xbd6b5)
at mono_conc_hashtable_insert (http://127.0.0.1:40487/_framework/dotnet.native.wasm:wasm-function[2199]:0xbd81d)
at mono_metadata_lookup_generic_class (http://127.0.0.1:40487/_framework/dotnet.native.wasm:wasm-function[2455]:0xd146e)
at inflate_generic_type (http://127.0.0.1:40487/_framework/dotnet.native.wasm:wasm-function[1235]:0x7313a)
at mono_class_inflate_generic_type_with_mempool (http://127.0.0.1:40487/_framework/dotnet.native.wasm:wasm-function[1234]:0x72a72)
at mono_class_inflate_generic_class_checked (http://127.0.0.1:40487/_framework/dotnet.native.wasm:wasm-function[1237]:0x73253)
at mono_class_get_and_inflate_typespec_checked (http://127.0.0.1:40487/_framework/dotnet.native.wasm:wasm-function[1293]:0x7533e)
I guess other places don't produce as nice message when they can't allocate
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: https://github.com/dotnet/runtime/pull/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: :mag_right: 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: :x: Known issue did not match with the provided build. Validation performed at: 4/25/2024 7:55:51 PM UTCReport
Summary