Error Blob
{
"ErrorMessage": "",
"BuildRetry": false,
"ErrorPattern": "\['WasmTestOnBrowser-[a-zA-Z0-9\._\-]+' END OF WORK ITEM LOG: Command timed out, and was killed\]",
"ExcludeConsoleLog": true
}Reproduction Steps
@radical this failure is very similar to #81170, but that one has no hits lately because the ExceptionTests were disabled in #81171.
This error I am seeing has a very similar failure message, it's happening in a windows, in 7.0, but the execution killed message happens in WasmTestOnBrowser instead of in chrome-DebuggerTests. Do you think this failure is the same as the one tracked by #81170?
...
...
[38/39] xunit.runner.utility.netcoreapp10.dll -> xunit.runner.utility.netcoreapp10.dll.bc
[39/39] xunit.execution.dotnet.dll -> xunit.execution.dotnet.dll.bc
...
[EXECUTION TIMED OUT]
Exit Code:-3Executor timed out after 3600 seconds and was killed, maybe it gives some idea:
['WasmTestOnBrowser-non-simd-System.Runtime.Intrinsics.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]
- But there's a third one that had this printed right before the execution was killed (log 3):
C:\helix\work\correlation\build\wasm\WasmApp.Native.targets(290,5):
warning WASM0001: Could not get pinvoke, or callbacks for method
'System.Tests.TimeZoneInfoTests+WindowsUILanguageHelper::EnumUILanguages'
because 'Parsing function pointer types in signatures is not supported.'
[C:\helix\work\workitem\e\publish\ProxyProjectForAOTOnHelix.proj]
...
[EXECUTION TIMED OUT]
Exit Code:-3Executor timed out after 3600 seconds and was killed
['WasmTestOnBrowser-System.Runtime.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]
Known Issue Error Message
Fill the error message using known issues guidance.
{
"ErrorMessage": "",
"BuildRetry": false
}Report
Summary
| 24-Hour Hit Count |
7-Day Hit Count |
1-Month Count |
| 0 |
0 |
0 |
Error Blob
{ "ErrorMessage": "", "BuildRetry": false, "ErrorPattern": "\['WasmTestOnBrowser-[a-zA-Z0-9\._\-]+' END OF WORK ITEM LOG: Command timed out, and was killed\]", "ExcludeConsoleLog": true }Reproduction Steps
@radical this failure is very similar to #81170, but that one has no hits lately because the ExceptionTests were disabled in #81171.
This error I am seeing has a very similar failure message, it's happening in a windows, in 7.0, but the
execution killedmessage happens inWasmTestOnBrowserinstead of inchrome-DebuggerTests. Do you think this failure is the same as the one tracked by #81170?runtime-staging: https://dev.azure.com/dnceng-public/public/_build/results?buildId=282556&view=resultsBuild Browser wasm windows Release LibraryTests_AOTKnown Issue Error Message
Fill the error message using known issues guidance.
{ "ErrorMessage": "", "BuildRetry": false }Report
Summary