Uh oh!
There was an error while loading. Please reload this page.
Disable the UTFStringConversionFailures test on CI runs - #114747
Conversation
…machines can't handle the load from allocating 2 2GB strings and the OOM killer was killing the process.
There was a problem hiding this comment.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
src/libraries/System.Runtime.InteropServices/tests/LibraryImportGenerator.Tests/CollectionMarshallingFails.cs:113
- Disabling the test reduces CI coverage; please ensure that issue #114241 tracks plans for addressing this or running the test in a memory-optimized environment.
[SkipOnCI("Allocates enough memory that the OOM killer can kill the process on our Helix machines.")]
Tagging subscribers to this area: @dotnet/interop-contrib |
| { | ||
| [Fact] | ||
| [SkipOnCI("Allocates enough memory that the OOM killer can kill the process on our Helix machines.")] | ||
| public void UTFStringConversionFailures() |
There was a problem hiding this comment.
Would it make sense to name this as something specific to conversion failures due to the long string?
jkoritzinsky
commented
Apr 17, 2025
/ba-g wasm failures unrelated |
jkoritzinsky
commented
Jun 10, 2025
/backport to release/9.0-staging |
Started backporting to release/9.0-staging: https://github.com/dotnet/runtime/actions/runs/15550434935 |
agocke
commented
Jul 10, 2025
/backport to release/8.0-staging |
Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/16183337745 |
Disable the UTFStringConversionFailures test on CI runs as our Helix machines can't handle the load from allocating 2 2GB strings and the OOM killer was killing the process.
Fixes#114241