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.

Sign up for GitHub

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

Ensure that the handling for the V128_BITCAST APIs is correctly performant on Mono WASM #105009

Merged
merged 1 commit into from
Jul 17, 2024

Ensure that the handling for the V128_BITCAST APIs is correctly perfo…

1c2b616
Select commit
Loading
Failed to load commit list.
Merged

Ensure that the handling for the V128_BITCAST APIs is correctly performant on Mono WASM #105009

Ensure that the handling for the V128_BITCAST APIs is correctly perfo…
1c2b616
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed Jul 17, 2024 in 2h 39m 23s

Build #20240716.227 had test failures

2 errors / 16 warnings

Details

Tests

  • Failed: 11 (0.00%)
  • Passed: 2,116,154 (97.75%)
  • Other: 48,796 (2.25%)
  • Total: 2,164,961

Annotations

Check failure on line 91 in .packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24360.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24360.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91 

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24360.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnChrome-MT-System.IO.FileSystem.Tests in job 9f133745-341e-4597-a35b-3cadf81fa521 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/9f133745-341e-4597-a35b-3cadf81fa521/workitems/WasmTestOnChrome-MT-System.IO.FileSystem.Tests/console

Check failure on line 91 in .packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24360.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24360.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91 

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24360.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnChrome-MT-System.Private.Xml.Tests in job 9f133745-341e-4597-a35b-3cadf81fa521 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/9f133745-341e-4597-a35b-3cadf81fa521/workitems/WasmTestOnChrome-MT-System.Private.Xml.Tests/console

Check failure on line 1 in Wasm.Build.Tests.BuildPublishTests.BuildThenPublishWithAOT(buildArgs: BuildArgs { ProjectName = placeholder, Config = Release, AOT = True, ProjectFileContents = placeholder, ExtraBuildArgs = }, host: Chrome, id: \"eb4ceje3_tuv\")

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Wasm.Build.Tests.BuildPublishTests.BuildThenPublishWithAOT(buildArgs: BuildArgs { ProjectName = placeholder, Config = Release, AOT = True, ProjectFileContents = placeholder, ExtraBuildArgs = }, host: Chrome, id: \"eb4ceje3_tuv\") 

System.AggregateException : One or more errors occurred. (A task was canceled.)
---- System.Threading.Tasks.TaskCanceledException : A task was canceled.
Raw output 
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait()
   at Wasm.Build.Tests.BuildTestBase.RunProcess(String path, ITestOutputHelper _testOutput, String args, IDictionary`2 envVars, String workingDir, String label, Nullable`1 timeoutMs) in /_/src/mono/wasm/Wasm.Build.Tests/BuildTestBase.cs:line 433
   at Wasm.Build.Tests.BuildTestBase.RunWithXHarness(String testCommand, String testLogPath, String projectName, String bundleDir, ITestOutputHelper _testOutput, IDictionary`2 envVars, Int32 expectedAppExitCode, Int32 xharnessExitCode, String extraXHarnessArgs, String appArgs, String extraXHarnessMonoArgs, Boolean useWasmConsoleOutput) in /_/src/mono/wasm/Wasm.Build.Tests/BuildTestBase.cs:line 298
   at Wasm.Build.Tests.BuildTestBase.RunAndTestWasmApp(BuildArgs buildArgs, RunHost host, String id, Action`1 test, String buildDir, String bundleDir, Int32 expectedExitCode, String args, Dictionary`2 envVars, String targetFramework, String extraXHarnessMonoArgs, String extraXHarnessArgs, String jsRelativePath, String environmentLocale) in /_/src/mono/wasm/Wasm.Build.Tests/BuildTestBase.cs:line 219
   at Wasm.Build.Tests.BuildPublishTests.<>c__DisplayClass3_0.<BuildThenPublishWithAOT>g__Run|3(Boolean expectAOT) in /_/src/mono/wasm/Wasm.Build.Tests/BuildPublishTests.cs:line 172
   at Wasm.Build.Tests.BuildPublishTests.BuildThenPublishWithAOT(BuildArgs buildArgs, RunHost host, String id) in /_/src/mono/wasm/Wasm.Build.Tests/BuildPublishTests.cs:line 126

   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)
----- Inner Stack Trace -----
   at System.Threading.Tasks.Task.GetExceptions(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait()
   at Wasm.Build.Tests.BuildTestBase.RunProcess(String path, ITestOutputHelper _testOutput, String args, IDictionary`2 envVars, String workingDir, String label, Nullable`1 timeoutMs) in /_/src/mono/wasm/Wasm.Build.Tests/BuildTestBase.cs:line 433
   at Wasm.Build.Tests.BuildTestBase.RunWithXHarness(String testCommand, String testLogPath, String projectName, String bundleDir, ITestOutputHelper _testOutput, IDictionary`2 envVars, Int32 expectedAppExitCode, Int32 xharnessExitCode, String extraXHarnessArgs, String appArgs, String extraXHarnessMonoArgs, Boolean useWasmConsoleOutput) in /_/src/mono/wasm/Wasm.Build.Tests/BuildTestBase.cs:line 298
   at Wasm.Build.Tests.BuildTestBase.RunAndTestWasmApp(BuildArgs buildArgs, RunHost host, String id, Action`1 test, String buildDir, String bundleDir, Int32 expectedExitCode, String args, Dictionary`2 envVars, String targetFramework, String extraXHarnessMonoArgs, String extraXHarnessArgs, String jsRelativePath, String environmentLocale) in /_/src/mono/wasm/Wasm.Build.Tests/BuildTestBase.cs:line 219
   at Wasm.Build.Tests.BuildPublishTests.<>c__DisplayClass3_0.<BuildThenPublishWithAOT>g__Run|3(Boolean expectAOT) in /_/src/mono/wasm/Wasm.Build.Tests/BuildPublishTests.cs:line 172
   at Wasm.Build.Tests.BuildPublishTests.BuildThenPublishWithAOT(BuildArgs buildArgs, RunHost host, String id) in /_/src/mono/wasm/Wasm.Build.Tests/BuildPublishTests.cs:line 126
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)
   at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder

Check failure on line 1 in Workloads-NoWebcil-ST-Wasm.Build.Tests.BuildPublishTests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Workloads-NoWebcil-ST-Wasm.Build.Tests.BuildPublishTests.WorkItemExecution 

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.

Check failure on line 1 in WasmTestOnChrome-MT-System.Private.Xml.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnChrome-MT-System.Private.Xml.Tests.WorkItemExecution 

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.

Check failure on line 1 in Workloads-NoWebcil-ST-Wasm.Build.Tests.TestAppScenarios.MemoryTests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Workloads-NoWebcil-ST-Wasm.Build.Tests.TestAppScenarios.MemoryTests.WorkItemExecution 

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.
View more details on Azure Pipelines