[wasm] Fix runtime tests build on CI #93646
Conversation
Runtime tests build for wasm started timing out recently, with the job getting cancelled, likely due to the build hitting the container limits. This changes the inner test builds to not run in parallel at all, with `/m:1`, which unblocks the CI at least. Issue: dotnet#93134
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsRuntime tests build for wasm started timing out recently, with the job This changes the inner test builds to not run in parallel at all, with Fixes issue: #93134
|
|
Tagging subscribers to this area: @hoyosjs Issue DetailsRuntime tests build for wasm started timing out recently, with the job This changes the inner test builds to not run in parallel at all, with Fixes issue: #93134
|
|
Tagging subscribers to this area: @directhex Issue DetailsRuntime tests build for wasm started timing out recently, with the job This changes the inner test builds to not run in parallel at all, with Fixes issue: #93134
|
|
|
…rrently built for wasm
|
I'm not sure why the failing test didn't get skipped. Any objections to merging this with the failed tests to unblock CI for runtime tests? |
|
Opened #93669 for the failing tests. |
ghost
locked as resolved and limited conversation to collaborators
Runtime tests build for wasm started timing out recently, with the job
getting cancelled, likely due to the build hitting the container limits.
This changes the inner test builds to not run in parallel at all, with
/m:1, which unblocks the CI at least.Fixes issue: #93134