Open radekdoulik opened 1 year ago
Tagging subscribers to this area: @directhex See info in area-owners.md if you want to be subscribed.
Author: | radekdoulik |
---|---|
Assignees: | - |
Labels: | `untriaged`, `area-Infrastructure-mono`, `runtime-mono`, `needs-area-label` |
Milestone: | 8.0.0 |
@radekdoulik the first error message is already being tracked with https://github.com/dotnet/runtime/issues/81383 : Handle collector count overflows or underflows.
. We are already tracking the hits of that one with Known Build Error.
For the second error message, can you please make sure this issue is linked with Known Build Error? The instructions can be found in our template: https://github.com/dotnet/runtime/issues/new?assignees=&labels=blocking-clean-ci%2CKnown+Build+Error&template=04_ci_known_issue.yml
@radekdoulik the first error message is already being tracked with #81383 :
Handle collector count overflows or underflows.
. We are already tracking the hits of that one with Known Build Error.For the second error message, can you please make sure this issue is linked with Known Build Error? The instructions can be found in our template: https://github.com/dotnet/runtime/issues/new?assignees=&labels=blocking-clean-ci%2CKnown+Build+Error&template=04_ci_known_issue.yml
These are now disabled on wasm, so they shouldn't fail on CI.
Looking at the logs, it also seems different than #81383, because in our case the tests passes, but xharness evaluates it as failed.
Tagging subscribers to 'arch-wasm': @lewing See info in area-owners.md if you want to be subscribed.
Author: | radekdoulik |
---|---|
Assignees: | - |
Labels: | `arch-wasm`, `area-Infrastructure-mono`, `runtime-mono` |
Milestone: | 8.0.0 |
@radekdoulik please update the status of this issue
@radekdoulik, should https://github.com/dotnet/runtime/pull/100334 try to enable the tests? Or a separate PR when the bump is merged.
These failures might be related to change in handling of
ExitStatus
exception in emscripten.Failing tests
Logs