Skip to content
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

Closed
radical opened this issue Sep 10, 2022 · 38 comments
Closed
Assignees
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' test-failure
Milestone

Comments

@radical
Copy link
Member

radical commented Sep 10, 2022

Occurrences:

Day Run OS Details
9/23 Rolling run 28406 (7.0) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 1x JIT.* failures
9/23 Rolling run 28106 (7.0) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 3x JIT.* failures
9/23 Rolling run 27711 (7.0) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 3x JIT.* failures
9/22 Rolling run 27252 (7.0) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 3x JIT.* failures
9/22 Rolling run 25951 (7.0) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 4x JIT.* failures
9/21 Rolling run 25763 (7.0) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 2x JIT.* failures
9/21 Rolling run 25169 (7.0) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 8x JIT.* failures
9/20 Rolling run 23284 (7.0) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 2x JIT.* failures
9/19 Rolling run 22992 (7.0) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 5x JIT.* failures
9/19 Rolling run 22495 (7.0) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 2x JIT failures & 1x Loader failure
9/17-9/18 no runs
9/16 Rolling run 20657 (7.0-rc2) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 2x JIT.* failures
9/16 Rolling run 20304 (7.0) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 3x JIT.* failures
9/16 Rolling run 20115 (7.0-rc2) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 1x Loader.* failure
9/15 Rolling run 18463 (7.0) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 1x JIT.* failure
9/15 Rolling run 18930 (7.0-rc2) Mono Browser wasm Release @ Ubuntu.1804.Amd64.Open 2x JIT.* failures

Original report

JIT.HardwareIntrinsics.Arm.AdvSimd:

    JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/AdvSimd_Part6_r.sh [FAIL]
      
      Return code:      1
      Raw output file:      /datadisks/disk1/work/B2CE09D6/w/ABBA093D/uploads/Reports/JIT.HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/AdvSimd_Part6_r.output.txt
      Raw output:
      BEGIN EXECUTION
      MSBuild version 17.4.0-preview-22416-02+5d102ae37 for .NET
        AppDir: /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/WasmApp/
        TestBinDir: /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r
        ArtifactsBinDir: 
        Generated app bundle at /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/WasmApp/
      /datadisks/disk1/work/B2CE09D6/p/dotnet-cli/sdk/7.0.100-rc.1.22425.9/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.RuntimeIdentifierInference.targets(219,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy [/datadisks/disk1/work/B2CE09D6/p/wasm-test-runner/WasmTestRunner.proj]
      Test Harness Exitcode is : 1
      To run the test:
      > set CORE_ROOT=/datadisks/disk1/work/B2CE09D6/p
      > /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/AdvSimd_Part6_r.sh
      Expected: True
      Actual:   False
      Stack Trace:
           at JIT_HardwareIntrinsics._Arm_AdvSimd_AdvSimd_Part6_r_AdvSimd_Part6_r_._Arm_AdvSimd_AdvSimd_Part6_r_AdvSimd_Part6_r_sh()
           at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
           at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
      Output:
        
        Return code:      1
        Raw output file:      /datadisks/disk1/work/B2CE09D6/w/ABBA093D/uploads/Reports/JIT.HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/AdvSimd_Part6_r.output.txt
        Raw output:
        BEGIN EXECUTION
        MSBuild version 17.4.0-preview-22416-02+5d102ae37 for .NET
          AppDir: /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/WasmApp/
          TestBinDir: /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r
          ArtifactsBinDir: 
          Generated app bundle at /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/WasmApp/
        /datadisks/disk1/work/B2CE09D6/p/dotnet-cli/sdk/7.0.100-rc.1.22425.9/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.RuntimeIdentifierInference.targets(219,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy [/datadisks/disk1/work/B2CE09D6/p/wasm-test-runner/WasmTestRunner.proj]
        Test Harness Exitcode is : 1
        To run the test:
        > set CORE_ROOT=/datadisks/disk1/work/B2CE09D6/p
        > /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/AdvSimd_Part6_r.sh

JIT.HardwareIntrinsics.X86.General:

    JIT/HardwareIntrinsics/X86/General/VectorUnused_r/VectorUnused_r.sh [FAIL]
      
      Return code:      1
      Raw output file:      /datadisks/disk1/work/B2CE09D6/w/AF3E0916/uploads/Reports/JIT.HardwareIntrinsics/X86/General/VectorUnused_r/VectorUnused_r.output.txt
      Raw output:
      BEGIN EXECUTION
      MSBuild version 17.4.0-preview-22416-02+5d102ae37 for .NET
      /datadisks/disk1/work/B2CE09D6/p/wasm-test-runner/WasmTestRunner.proj : error : Failed to resolve SDK 'Microsoft.Build.NoTargets/1.0.53'. Package restore was successful but a package with the ID of "Microsoft.Build.NoTargets" was not installed.
      /datadisks/disk1/work/B2CE09D6/p/wasm-test-runner/WasmTestRunner.proj : error MSB4236: The SDK 'Microsoft.Build.NoTargets/1.0.53' specified could not be found.
      Test Harness Exitcode is : 1
      To run the test:
      > set CORE_ROOT=/datadisks/disk1/work/B2CE09D6/p
      > /datadisks/disk1/work/B2CE09D6/w/AF3E0916/e/JIT/HardwareIntrinsics/X86/General/VectorUnused_r/VectorUnused_r.sh
      Expected: True
      Actual:   False
      Stack Trace:
           at JIT_HardwareIntrinsics._X86_General_VectorUnused_r_VectorUnused_r_._X86_General_VectorUnused_r_VectorUnused_r_sh()
           at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
           at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
      Output:
        
        Return code:      1
        Raw output file:      /datadisks/disk1/work/B2CE09D6/w/AF3E0916/uploads/Reports/JIT.HardwareIntrinsics/X86/General/VectorUnused_r/VectorUnused_r.output.txt
        Raw output:
        BEGIN EXECUTION
        MSBuild version 17.4.0-preview-22416-02+5d102ae37 for .NET
        /datadisks/disk1/work/B2CE09D6/p/wasm-test-runner/WasmTestRunner.proj : error : Failed to resolve SDK 'Microsoft.Build.NoTargets/1.0.53'. Package restore was successful but a package with the ID of "Microsoft.Build.NoTargets" was not installed.
        /datadisks/disk1/work/B2CE09D6/p/wasm-test-runner/WasmTestRunner.proj : error MSB4236: The SDK 'Microsoft.Build.NoTargets/1.0.53' specified could not be found.
        Test Harness Exitcode is : 1
        To run the test:
        > set CORE_ROOT=/datadisks/disk1/work/B2CE09D6/p
        > /datadisks/disk1/work/B2CE09D6/w/AF3E0916/e/JIT/HardwareIntrinsics/X86/General/VectorUnused_r/VectorUnused_r.sh
  Finished:    JIT.HardwareIntrinsics.XUnitWrapper

JIT.HardwareIntrinsics.X86.Ssse3:

      Unhandled exception: System.IO.IOException: Connection timed out : 'Global\msbuild-server-launch-aCL7KKV98jx3O3fvRayafjy8_eCkKjpwtyjOVymKcEE'
         at System.Threading.Mutex.CreateMutexCore(Boolean initiallyOwned, String name, Boolean& createdNew)
         at Microsoft.Build.Experimental.MSBuildClient.TryLaunchServer()
         at Microsoft.Build.Experimental.MSBuildClient.Execute(CancellationToken cancellationToken)
         at Microsoft.Build.CommandLine.MSBuildClientApp.Execute(String[] commandLine, String msbuildLocation, CancellationToken cancellationToken)
         at Microsoft.Build.CommandLine.MSBuildApp.Main(String[] args)
         at Microsoft.DotNet.Cli.Utils.MSBuildForwardingAppWithoutLogging.ExecuteInProc(String[] arguments)
      
      Return code:      82
      Raw output file:      /datadisks/disk1/work/B2CE09D6/w/B25B099A/uploads/Reports/JIT.HardwareIntrinsics/X86/Ssse3/Ssse3_ro/Ssse3_ro.output.txt
...

JIT.Regression.CLR-x86-JIT.V1-M12-M13:

    JIT/Regression/CLR-x86-JIT/V1-M13-RTM/b92289/b92289/b92289.sh [FAIL]
      Unhandled exception: System.IO.IOException: Connection timed out : 'Global\msbuild-server-launch-aCL7KKV98jx3O3fvRayafjy8_eCkKjpwtyjOVymKcEE'
         at System.Threading.Mutex.CreateMutexCore(Boolean initiallyOwned, String name, Boolean& createdNew)
         at Microsoft.Build.Experimental.MSBuildClient.TryLaunchServer()
         at Microsoft.Build.Experimental.MSBuildClient.Execute(CancellationToken cancellationToken)
         at Microsoft.Build.CommandLine.MSBuildClientApp.Execute(String[] commandLine, String msbuildLocation, CancellationToken cancellationToken)
         at Microsoft.Build.CommandLine.MSBuildApp.Main(String[] args)
         at Microsoft.DotNet.Cli.Utils.MSBuildForwardingAppWithoutLogging.ExecuteInProc(String[] arguments)

... followed by lot of failures ...

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
@radical radical added arch-wasm WebAssembly architecture blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' area-VM-meta-mono test-failure labels Sep 10, 2022
@ghost
Copy link

ghost commented Sep 10, 2022

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

JIT.HardwareIntrinsics.Arm.AdvSimd:

    JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/AdvSimd_Part6_r.sh [FAIL]
      
      Return code:      1
      Raw output file:      /datadisks/disk1/work/B2CE09D6/w/ABBA093D/uploads/Reports/JIT.HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/AdvSimd_Part6_r.output.txt
      Raw output:
      BEGIN EXECUTION
      MSBuild version 17.4.0-preview-22416-02+5d102ae37 for .NET
        AppDir: /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/WasmApp/
        TestBinDir: /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r
        ArtifactsBinDir: 
        Generated app bundle at /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/WasmApp/
      /datadisks/disk1/work/B2CE09D6/p/dotnet-cli/sdk/7.0.100-rc.1.22425.9/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.RuntimeIdentifierInference.targets(219,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy [/datadisks/disk1/work/B2CE09D6/p/wasm-test-runner/WasmTestRunner.proj]
      Test Harness Exitcode is : 1
      To run the test:
      > set CORE_ROOT=/datadisks/disk1/work/B2CE09D6/p
      > /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/AdvSimd_Part6_r.sh
      Expected: True
      Actual:   False
      Stack Trace:
           at JIT_HardwareIntrinsics._Arm_AdvSimd_AdvSimd_Part6_r_AdvSimd_Part6_r_._Arm_AdvSimd_AdvSimd_Part6_r_AdvSimd_Part6_r_sh()
           at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
           at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
      Output:
        
        Return code:      1
        Raw output file:      /datadisks/disk1/work/B2CE09D6/w/ABBA093D/uploads/Reports/JIT.HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/AdvSimd_Part6_r.output.txt
        Raw output:
        BEGIN EXECUTION
        MSBuild version 17.4.0-preview-22416-02+5d102ae37 for .NET
          AppDir: /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/WasmApp/
          TestBinDir: /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r
          ArtifactsBinDir: 
          Generated app bundle at /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/WasmApp/
        /datadisks/disk1/work/B2CE09D6/p/dotnet-cli/sdk/7.0.100-rc.1.22425.9/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.RuntimeIdentifierInference.targets(219,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy [/datadisks/disk1/work/B2CE09D6/p/wasm-test-runner/WasmTestRunner.proj]
        Test Harness Exitcode is : 1
        To run the test:
        > set CORE_ROOT=/datadisks/disk1/work/B2CE09D6/p
        > /datadisks/disk1/work/B2CE09D6/w/ABBA093D/e/JIT/HardwareIntrinsics/Arm/AdvSimd/AdvSimd_Part6_r/AdvSimd_Part6_r.sh

JIT.HardwareIntrinsics.X86.General:

    JIT/HardwareIntrinsics/X86/General/VectorUnused_r/VectorUnused_r.sh [FAIL]
      
      Return code:      1
      Raw output file:      /datadisks/disk1/work/B2CE09D6/w/AF3E0916/uploads/Reports/JIT.HardwareIntrinsics/X86/General/VectorUnused_r/VectorUnused_r.output.txt
      Raw output:
      BEGIN EXECUTION
      MSBuild version 17.4.0-preview-22416-02+5d102ae37 for .NET
      /datadisks/disk1/work/B2CE09D6/p/wasm-test-runner/WasmTestRunner.proj : error : Failed to resolve SDK 'Microsoft.Build.NoTargets/1.0.53'. Package restore was successful but a package with the ID of "Microsoft.Build.NoTargets" was not installed.
      /datadisks/disk1/work/B2CE09D6/p/wasm-test-runner/WasmTestRunner.proj : error MSB4236: The SDK 'Microsoft.Build.NoTargets/1.0.53' specified could not be found.
      Test Harness Exitcode is : 1
      To run the test:
      > set CORE_ROOT=/datadisks/disk1/work/B2CE09D6/p
      > /datadisks/disk1/work/B2CE09D6/w/AF3E0916/e/JIT/HardwareIntrinsics/X86/General/VectorUnused_r/VectorUnused_r.sh
      Expected: True
      Actual:   False
      Stack Trace:
           at JIT_HardwareIntrinsics._X86_General_VectorUnused_r_VectorUnused_r_._X86_General_VectorUnused_r_VectorUnused_r_sh()
           at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
           at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
      Output:
        
        Return code:      1
        Raw output file:      /datadisks/disk1/work/B2CE09D6/w/AF3E0916/uploads/Reports/JIT.HardwareIntrinsics/X86/General/VectorUnused_r/VectorUnused_r.output.txt
        Raw output:
        BEGIN EXECUTION
        MSBuild version 17.4.0-preview-22416-02+5d102ae37 for .NET
        /datadisks/disk1/work/B2CE09D6/p/wasm-test-runner/WasmTestRunner.proj : error : Failed to resolve SDK 'Microsoft.Build.NoTargets/1.0.53'. Package restore was successful but a package with the ID of "Microsoft.Build.NoTargets" was not installed.
        /datadisks/disk1/work/B2CE09D6/p/wasm-test-runner/WasmTestRunner.proj : error MSB4236: The SDK 'Microsoft.Build.NoTargets/1.0.53' specified could not be found.
        Test Harness Exitcode is : 1
        To run the test:
        > set CORE_ROOT=/datadisks/disk1/work/B2CE09D6/p
        > /datadisks/disk1/work/B2CE09D6/w/AF3E0916/e/JIT/HardwareIntrinsics/X86/General/VectorUnused_r/VectorUnused_r.sh
  Finished:    JIT.HardwareIntrinsics.XUnitWrapper

JIT.HardwareIntrinsics.X86.Ssse3:

      Unhandled exception: System.IO.IOException: Connection timed out : 'Global\msbuild-server-launch-aCL7KKV98jx3O3fvRayafjy8_eCkKjpwtyjOVymKcEE'
         at System.Threading.Mutex.CreateMutexCore(Boolean initiallyOwned, String name, Boolean& createdNew)
         at Microsoft.Build.Experimental.MSBuildClient.TryLaunchServer()
         at Microsoft.Build.Experimental.MSBuildClient.Execute(CancellationToken cancellationToken)
         at Microsoft.Build.CommandLine.MSBuildClientApp.Execute(String[] commandLine, String msbuildLocation, CancellationToken cancellationToken)
         at Microsoft.Build.CommandLine.MSBuildApp.Main(String[] args)
         at Microsoft.DotNet.Cli.Utils.MSBuildForwardingAppWithoutLogging.ExecuteInProc(String[] arguments)
      
      Return code:      82
      Raw output file:      /datadisks/disk1/work/B2CE09D6/w/B25B099A/uploads/Reports/JIT.HardwareIntrinsics/X86/Ssse3/Ssse3_ro/Ssse3_ro.output.txt
...

JIT.Regression.CLR-x86-JIT.V1-M12-M13:

    JIT/Regression/CLR-x86-JIT/V1-M13-RTM/b92289/b92289/b92289.sh [FAIL]
      Unhandled exception: System.IO.IOException: Connection timed out : 'Global\msbuild-server-launch-aCL7KKV98jx3O3fvRayafjy8_eCkKjpwtyjOVymKcEE'
         at System.Threading.Mutex.CreateMutexCore(Boolean initiallyOwned, String name, Boolean& createdNew)
         at Microsoft.Build.Experimental.MSBuildClient.TryLaunchServer()
         at Microsoft.Build.Experimental.MSBuildClient.Execute(CancellationToken cancellationToken)
         at Microsoft.Build.CommandLine.MSBuildClientApp.Execute(String[] commandLine, String msbuildLocation, CancellationToken cancellationToken)
         at Microsoft.Build.CommandLine.MSBuildApp.Main(String[] args)
         at Microsoft.DotNet.Cli.Utils.MSBuildForwardingAppWithoutLogging.ExecuteInProc(String[] arguments)

... followed by lot of failures ...
Author: radical
Assignees: -
Labels:

arch-wasm, blocking-clean-ci, area-VM-meta-mono, test-failure

Milestone: -

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Sep 10, 2022
@stephentoub
Copy link
Member

Also on PRs in main, e.g.
https://github.com/dotnet/runtime/pull/75318/checks?check_run_id=8279068492
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-75318-merge-3cb5f6cbea0a472187/JIT.HardwareIntrinsics.General.Vector256/1/console.f2f14acf.log?helixlogtype=result

      > /datadisks/disk1/work/B89F09F9/w/BCB50A0C/e/JIT/HardwareIntrinsics/General/Vector256_1/Vector256_1_ro/Vector256_1_ro.sh
      Expected: True
      Actual:   False
      Stack Trace:
           at JIT_HardwareIntrinsics._General_Vector256_1_Vector256_1_ro_Vector256_1_ro_._General_Vector256_1_Vector256_1_ro_Vector256_1_ro_sh()
           at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
           at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)

@radical
Copy link
Member Author

radical commented Sep 10, 2022

And build, log:

    JIT/Regression/JitBlue/Runtime_74126/Runtime_74126/Runtime_74126.sh [FAIL]
      
      Unhandled Exception:
      System.NullReferenceException: Object reference not set to an instance of an object
         at Runtime_74126.GetVtor[Vector256`1](Vector256`1 vtor)
         at Runtime_74126.Main()
      [ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
         at Runtime_74126.GetVtor[Vector256`1](Vector256`1 vtor)
         at Runtime_74126.Main()
      
      Return code:      1
      Raw output file:      /datadisks/disk1/work/B6FB09E0/w/BC8609F2/uploads/Reports/JIT.Regression/JitBlue/Runtime_74126/Runtime_74126/Runtime_74126.output.txt
      Raw output:
      BEGIN EXECUTION
      /datadisks/disk1/work/B6FB09E0/p/corerun -p System.Reflection.Metadata.MetadataUpdater.IsSupported=false Runtime_74126.dll ''
      Expected: 100
      Actual: 1
      END EXECUTION - FAILED
...

@danmoseley danmoseley added this to the 7.0.0 milestone Sep 10, 2022
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Sep 10, 2022
@lewing
Copy link
Member

lewing commented Sep 10, 2022

This seems to have come in with the new sdk

@lewing
Copy link
Member

lewing commented Sep 10, 2022

cc @rainersigwald

@lewing
Copy link
Member

lewing commented Sep 14, 2022

I think we should try setting DOTNET_CLI_DO_NOT_USE_MSBUILD_SERVER=true and see what happens here

@carlossanlop
Copy link
Member

carlossanlop commented Sep 16, 2022

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.HardwareIntrinsics.Arm.AdvSimd/console

Failure log: https://helix.dot.net/api/2019-06-17/jobs/65f2f4ec-4e82-480f-9f8b-ca6855cbff9b/workitems/JIT.HardwareIntrinsics.Arm.Dp/console

Failure log: https://helix.dot.net/api/2019-06-17/jobs/65f2f4ec-4e82-480f-9f8b-ca6855cbff9b/workitems/JIT.HardwareIntrinsics.General.NotSupported/console

Failure log: https://helix.dot.net/api/2019-06-17/jobs/65f2f4ec-4e82-480f-9f8b-ca6855cbff9b/workitems/JIT.HardwareIntrinsics.X86.Avx1/console

Failure log: https://helix.dot.net/api/2019-06-17/jobs/65f2f4ec-4e82-480f-9f8b-ca6855cbff9b/workitems/JIT.HardwareIntrinsics.X86.Sse2/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

@lewing
Copy link
Member

lewing commented Sep 19, 2022

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?

@karelz

This comment was marked as duplicate.

@lewing
Copy link
Member

lewing commented Sep 23, 2022

have we seen this in main after #75743 ?

@karelz
Copy link
Member

karelz commented Sep 23, 2022

I just started updating top post with occurrences from Test Monitoring.
I never saw this particular category in main. First 7.0 occurrences happened on 9/15.

@lewing
Copy link
Member

lewing commented Sep 23, 2022

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.

@lewing
Copy link
Member

lewing commented Sep 23, 2022

@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

@lewing
Copy link
Member

lewing commented Sep 23, 2022

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

@naricc
Copy link
Member

naricc commented Sep 23, 2022

@rokonec I can also help walkthrough how the wasm runtime tests are built.

I think some of these errors may have been fixed by #75939.

Honestly reading through the issue I am a little confused about what failure we are actually trying to resolve?

@naricc
Copy link
Member

naricc commented Sep 23, 2022

@rokonec
A rough description of the wasm runtime tests. Each test is an individual project. When the tests are built, a xunit wrapper and bash wrapper are generated. When run, the xunit wrapper calls the shell script, and the shell script calls msbuild on this project to actually bundle all the assemblies into a wasm app. Finally, it runs the app. Note the oddity that we are doing a build step at test run time, so this all happens on helix.

The actual command to build the wasm app is generated from this part of the template:

$__Command msbuild $CORE_ROOT/wasm-test-runner/WasmTestRunner.proj /p:NetCoreAppCurrent=$(NetCoreAppCurrent) /p:TestAssemblyFileName=$(MsBuildProjectName).dll /p:TestBinDir=`pwd` $(CLRTestMSBuildArgs) || exit $?

Are there other details I can provide?

@lewing
Copy link
Member

lewing commented Sep 23, 2022

I'll add that often the projects are the same code with slightly different msbuild properties

@karelz
Copy link
Member

karelz commented Sep 23, 2022

@naricc

Honestly reading through the issue I am a little confused about what failure we are actually trying to resolve?

Check the top post -- all the 3 original kind of errors are captured in the table:

  • Unhandled exception: System.IO.IOException: Connection timed out
  • error : Failed to resolve SDK 'Microsoft.Build.NoTargets/1.0.53'. Package restore was successful but a package with the ID of "Microsoft.Build.NoTargets" was not installed.
  • Test Harness Exitcode is : 1 from Assert

github-actions bot pushed a commit that referenced this issue Sep 23, 2022
This will also avoid intermittent failures like #75391
@radical
Copy link
Member Author

radical commented Sep 23, 2022

I'm backporting #76107 which would remove the whole NoTargets issue.

lewing pushed a commit that referenced this issue Sep 24, 2022
This will also avoid intermittent failures like #75391

Co-authored-by: Ankit Jain <radical@gmail.com>
@rainersigwald
Copy link
Member

For Unhandled exception: System.IO.IOException: Connection timed out, the MSBuild fix (dotnet/msbuild#8000) is in, and flowed to SDK (dotnet/sdk#28125). Can runtime update to the latest SDK (7.0.100/GA) daily build in the hope that's fully resolved?

@radical
Copy link
Member Author

radical commented Sep 27, 2022

For Unhandled exception: System.IO.IOException: Connection timed out, the MSBuild fix (dotnet/msbuild#8000) is in, and flowed to SDK (dotnet/sdk#28125). Can runtime update to the latest SDK (7.0.100/GA) daily build in the hope that's fully resolved?

What's the name of the channel for this? .NET 7?

@rainersigwald
Copy link
Member

For Unhandled exception: System.IO.IOException: Connection timed out, the MSBuild fix (dotnet/msbuild#8000) is in, and flowed to SDK (dotnet/sdk#28125). Can runtime update to the latest SDK (7.0.100/GA) daily build in the hope that's fully resolved?

What's the name of the channel for this? .NET 7?

I don't know--@marcpopMSFT, do you?

@marcpopMSFT
Copy link
Member

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.

@lewing
Copy link
Member

lewing commented Oct 8, 2022

more discussion happening here #76736

radical added a commit that referenced this issue Nov 14, 2022
This will also avoid intermittent failures like #75391
# Conflicts:
#	src/tests/Common/wasm-test-runner/WasmTestRunner.proj
carlossanlop added a commit that referenced this issue Nov 15, 2022
…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>
@jkotas
Copy link
Member

jkotas commented Nov 30, 2022

Fixed by updating to .NET 7 GA that has msbuild server disabled.

@jkotas jkotas closed this as completed Nov 30, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Dec 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' test-failure
Projects
None yet
Development

No branches or pull requests