-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/7.0][wasm] Multiple JIT.*
runtime test failures on rolling builds
#75391
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsJIT.HardwareIntrinsics.Arm.AdvSimd:
JIT.HardwareIntrinsics.X86.General:
JIT.HardwareIntrinsics.X86.Ssse3:
JIT.Regression.CLR-x86-JIT.V1-M12-M13:
|
Also on PRs in main, e.g.
|
|
|
I think we should try setting |
Are all these JIT failures closely related enough to be grouped into a single issue? Anyway, I found a bunch of other failures in this release/7.0-rc2 backport PR: #75675
Failure log: https://helix.dot.net/api/2019-06-17/jobs/65f2f4ec-4e82-480f-9f8b-ca6855cbff9b/workitems/JIT.1/console Failure log: https://helix.dot.net/api/2019-06-17/jobs/65f2f4ec-4e82-480f-9f8b-ca6855cbff9b/workitems/JIT.Math/console Failure log: https://helix.dot.net/api/2019-06-17/jobs/65f2f4ec-4e82-480f-9f8b-ca6855cbff9b/workitems/JIT.Regression/console |
Also found a bunch of JIT failures in this other release/7.0-rc2 backport PR: #75761
Logs:
|
These all appear to be intermittent runtime tests where msbuild exits with a 1 instead of a 0 and there are also often accompanying restore failures on some tests that would have broken in every single test if it was a real issue. The failures also appear to be more related to how we build the wasm runtime tests than actual failures in the tests (if some of these tests were legitimately broken many other tests would have also failed). It is interesting that this seems to be happening much more on the release branches than main now? |
This comment was marked as duplicate.
This comment was marked as duplicate.
have we seen this in main after #75743 ? |
I just started updating top post with occurrences from Test Monitoring. |
There have been multiple roslyn/msbuild issues (and some caused by ubuntu's openSSL). I say we take #76090 for now and see if things go green. The failures here are definitely build related, if op_Equality was actually failing intermittently we'd see it in all the tests not just these. |
@jkoritzinsky @trylek can you help walk @rokonec through how the runtime tests build for wasm and why they might trigger interesting failures in the build/compiler servers |
if these are all on ubuntu 1804 it may be the openssl issue #48411 (comment) and https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1983100 but I think that had a specific exit code |
@rokonec The actual command to build the wasm app is generated from this part of the template:
Are there other details I can provide? |
I'll add that often the projects are the same code with slightly different msbuild properties |
Check the top post -- all the 3 original kind of errors are captured in the table:
|
This will also avoid intermittent failures like #75391
I'm backporting #76107 which would remove the whole NoTargets issue. |
This will also avoid intermittent failures like #75391 Co-authored-by: Ankit Jain <radical@gmail.com>
For |
What's the name of the channel for this? |
I don't know--@marcpopMSFT, do you? |
FYI, I posted internally but there not an installer build that has the msbuild change yet as the mirror was broken so code hasn't been flowing for rtm for a number of days now. I'll let you know once there is. |
more discussion happening here #76736 |
This will also avoid intermittent failures like #75391 # Conflicts: # src/tests/Common/wasm-test-runner/WasmTestRunner.proj
…8062) * Update dependencies from https://github.com/dotnet/emsdk build 20221108.3 Microsoft.NET.Workload.Emscripten.Manifest-6.0.100 , Microsoft.NET.Workload.Emscripten.Manifest-6.0.300 , Microsoft.NET.Workload.Emscripten.Manifest-6.0.400 From Version 6.0.11 -> To Version 6.0.12 * Update dependencies from https://github.com/dotnet/arcade build 20221108.2 Microsoft.DotNet.ApiCompat , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.TargetFramework.Sdk , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions From Version 6.0.0-beta.22512.3 -> To Version 6.0.0-beta.22558.2 * Reverting the source-build.yml changes causing the banana rid failure. * Update dependencies from https://github.com/dotnet/arcade build 20221108.7 Microsoft.DotNet.ApiCompat , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.TargetFramework.Sdk , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions From Version 6.0.0-beta.22512.3 -> To Version 6.0.0-beta.22558.7 * Update dependencies from https://github.com/dotnet/arcade build 20221110.1 Microsoft.DotNet.ApiCompat , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.TargetFramework.Sdk , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions From Version 6.0.0-beta.22512.3 -> To Version 6.0.0-beta.22560.1 * Update dependencies from https://github.com/dotnet/arcade build 20221111.1 Microsoft.DotNet.ApiCompat , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.TargetFramework.Sdk , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions From Version 6.0.0-beta.22512.3 -> To Version 6.0.0-beta.22561.1 * [wasm] Don't use MS.Build.NoTargets SDK for runtime tests (#75939) This will also avoid intermittent failures like #75391 # Conflicts: # src/tests/Common/wasm-test-runner/WasmTestRunner.proj Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com> Co-authored-by: Carlos Sanchez <1175054+carlossanlop@users.noreply.github.com> Co-authored-by: Ankit Jain <radical@gmail.com>
Fixed by updating to .NET 7 GA that has msbuild server disabled. |
Occurrences:
Original report
JIT.HardwareIntrinsics.Arm.AdvSimd:
JIT.HardwareIntrinsics.X86.General:
JIT.HardwareIntrinsics.X86.Ssse3:
JIT.Regression.CLR-x86-JIT.V1-M12-M13:
Report
Summary
The text was updated successfully, but these errors were encountered: