Ilona Tomkowicz
Ilona Tomkowicz
The real error: https://github.com/dotnet/runtime/blob/3f607bd6061299a20d29b76914b4176b9d835f66/src/libraries/System.Collections.Specialized/src/Resources/Strings.resx#L64 We have to figure out what `foreach` loop has caused it and change it to `for`. The test itself? https://github.com/dotnet/runtime/blob/3f607bd6061299a20d29b76914b4176b9d835f66/src/libraries/Common/tests/System/Collections/IEnumerable.NonGeneric.Tests.cs#L376 I cannot reproduce locally running on...
No hits after llvm bump, closing.
[8.0] Build failure in Workloads-NoWebcil-Wasm.Build.NativeRebuild.Tests.OptimizationFlagChangeTests
It never hit anything, I cannot find an error in the pattern, though.
[8.0] Build failure in Workloads-NoWebcil-Wasm.Build.NativeRebuild.Tests.OptimizationFlagChangeTests
Updated the message based on the common parts of the original and newest log.
[8.0] Build failure in Workloads-NoWebcil-Wasm.Build.NativeRebuild.Tests.OptimizationFlagChangeTests
It is a duplicate of https://github.com/dotnet/runtime/issues/104827.
This is not `HybridGlobalization` related failure but NodeJS related. It complains about passing `-engine-arg=--experimental-wasm-simd --engine-arg=--experimental-wasm-eh` in WBT.
Should get fixed by https://github.com/dotnet/runtime/pull/111655 (8.0 was hit only once, all the other failures are 9.0)
> maybe we can just disable NodeJS legs That's done, isn't it? https://github.com/dotnet/runtime/pull/108582
> maybe we can just disable NodeJS legs https://github.com/dotnet/runtime/pull/120195 https://github.com/dotnet/runtime/pull/120193
This was hit only twice just after reporting and not any more: #### Summary |24-Hour Hit Count|7-Day Hit Count|1-Month Count| |---|---|---| |0|0|2|