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

Jump to bottom

[wasm] WBT tests failing because of missing test app output #93583

Closed
radical opened this issue Oct 17, 2023 · 4 comments
Closed

[wasm] WBT tests failing because of missing test app output #93583

radical opened this issue Oct 17, 2023 · 4 comments
Assignees
@pavelsavara
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono Known Build Error Use this to report build issues in the .NET Helix tab

Comments

@radical
Copy link
Member

radical commented Oct 17, 2023 •
edited by build-analysis bot
Loading

Build, and log:

    Wasm.Build.Tests.WasmBuildAppTest.PropertiesFromRuntimeConfigJson(buildArgs: BuildArgs { ProjectName = placeholder, Config = Release, AOT = False, ProjectFileContents = placeholder, ExtraBuildArgs =  }, host: Chrome, id: "4lpskvor_yvt") [FAIL]
      Assert.Contains() Failure
      Not found: test_runtimeconfig_json: 25

..

                 [wasm test-browser] info: Application arguments: --run runtime_config_Release_False.dll
                 [wasm test-browser] info: Silently starting separate runtime instance as another ES6 module to populate caches...
                 [wasm test-browser] info: MONO_WASM: forceDisposeProxies done: 0 imports, 0 exports, 0 GCHandles, 0 JSHandles.
                 [wasm test-browser] info: browser: [main] Console websocket connected.
                 [wasm test-browser] info: Initializing dotnet version 9.0.0-ci commit hash 45ed0ab41c138ad1683b333b5b937b8240f3e4d8
                 [wasm test-browser] info: test-main.js exiting runtime_config_Release_False.dll with result 42
                 [wasm test-browser] info: http://127.0.0.1:49387/_framework/dotnet.js 2:1372 Array(1)
                 [wasm test-browser] info: WASM EXIT 42
                 [wasm test-browser] dbug: Reached wasm exit
                 [wasm test-browser] info: Waiting to flush log messages with a timeout of 120 secs ..
                 [wasm test-browser] warn: Message processor is not running anymore.
                 [wasm test-browser] info: {"method":"console.info","payload":"WASM EXIT 42","arguments":[]}
                 [wasm test-browser] dbug: Reading console messages from websocket stopped
                 [wasm test-browser] dbug: Failed trying to read log messages via selenium: OpenQA.Selenium.WebDriverException: invalid session id
                 [wasm test-browser]          at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
                 [wasm test-browser]          at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
                 [wasm test-browser]          at OpenQA.Selenium.Remote.RemoteWebDriver.InternalExecute(String driverCommandToExecute, Dictionary`2 parameters)
                 [wasm test-browser]          at OpenQA.Selenium.Remote.RemoteLogs.GetLog(String logKind)
                 [wasm test-browser]          at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmBrowserTestRunner.RunSeleniumLogMessagePump(IWebDriver driver, CancellationToken token) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/Browser/WasmBrowserTestRunner.cs:line 214
                 [wasm test-browser] dbug: Saving diagnostics data to 'C:\helix\work\workitem\e\diagnostics.json'

Diff since the last good commit for rolling builds: 44a2b2d...45ed0ab which includes #93010 for which the PR had a similar failure but the PR was merged on red.

cc @pavelsavara

Known Issue Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "",
  "ErrorPattern": "Not found: test_runtimeconfig_json: 25|Not found: Hashed: |Not found: args#: 2|Not found: Could not create es-ES culture",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=440172
Error message validated: Not found: test_runtimeconfig_json: 25|Not found: Hashed: |Not found: args#: 2|Not found: Could not create es-ES culture
Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 10/17/2023 1:25:04 AM UTC

Report

Build Definition Test Pull Request
441599 dotnet/runtime Workloads-NoWebcil-Wasm.Build.Tests.MainWithArgsTests.WorkItemExecution
441403 dotnet/runtime Workloads-Wasm.Build.Tests.MainWithArgsTests.WorkItemExecution #93066
441571 dotnet/runtime Workloads-Wasm.Build.Tests.MainWithArgsTests.WorkItemExecution #93571
441216 dotnet/runtime Workloads-NoWebcil-Wasm.Build.Tests.WasmBuildAppTest.WorkItemExecution #93606
441152 dotnet/runtime Workloads-NoWebcil-Wasm.Build.Tests.MainWithArgsTests.WorkItemExecution #93558
440565 dotnet/runtime Workloads-NoWebcil-Wasm.Build.Tests.MainWithArgsTests.WorkItemExecution #93182
440539 dotnet/runtime Workloads-NoWebcil-Wasm.Build.Tests.WasmBuildAppTest.WorkItemExecution #93571
440404 dotnet/runtime Workloads-Wasm.Build.Tests.NativeLibraryTests.WorkItemExecution #92095
439521 dotnet/runtime Workloads-Wasm.Build.Tests.MainWithArgsTests.WorkItemExecution #93280

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
7 9 9
@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 Known Build Error Use this to report build issues in the .NET Helix tab labels Oct 17, 2023
@ghost
Copy link

ghost commented Oct 17, 2023

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

Issue Details

Log:

    Wasm.Build.Tests.WasmBuildAppTest.PropertiesFromRuntimeConfigJson(buildArgs: BuildArgs { ProjectName = placeholder, Config = Release, AOT = False, ProjectFileContents = placeholder, ExtraBuildArgs =  }, host: Chrome, id: "4lpskvor_yvt") [FAIL]
      Assert.Contains() Failure
      Not found: test_runtimeconfig_json: 25

..

                 [wasm test-browser] info: Application arguments: --run runtime_config_Release_False.dll
                 [wasm test-browser] info: Silently starting separate runtime instance as another ES6 module to populate caches...
                 [wasm test-browser] info: MONO_WASM: forceDisposeProxies done: 0 imports, 0 exports, 0 GCHandles, 0 JSHandles.
                 [wasm test-browser] info: browser: [main] Console websocket connected.
                 [wasm test-browser] info: Initializing dotnet version 9.0.0-ci commit hash 45ed0ab41c138ad1683b333b5b937b8240f3e4d8
                 [wasm test-browser] info: test-main.js exiting runtime_config_Release_False.dll with result 42
                 [wasm test-browser] info: http://127.0.0.1:49387/_framework/dotnet.js 2:1372 Array(1)
                 [wasm test-browser] info: WASM EXIT 42
                 [wasm test-browser] dbug: Reached wasm exit
                 [wasm test-browser] info: Waiting to flush log messages with a timeout of 120 secs ..
                 [wasm test-browser] warn: Message processor is not running anymore.
                 [wasm test-browser] info: {"method":"console.info","payload":"WASM EXIT 42","arguments":[]}
                 [wasm test-browser] dbug: Reading console messages from websocket stopped
                 [wasm test-browser] dbug: Failed trying to read log messages via selenium: OpenQA.Selenium.WebDriverException: invalid session id
                 [wasm test-browser]          at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
                 [wasm test-browser]          at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
                 [wasm test-browser]          at OpenQA.Selenium.Remote.RemoteWebDriver.InternalExecute(String driverCommandToExecute, Dictionary`2 parameters)
                 [wasm test-browser]          at OpenQA.Selenium.Remote.RemoteLogs.GetLog(String logKind)
                 [wasm test-browser]          at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmBrowserTestRunner.RunSeleniumLogMessagePump(IWebDriver driver, CancellationToken token) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/Browser/WasmBrowserTestRunner.cs:line 214
                 [wasm test-browser] dbug: Saving diagnostics data to 'C:\helix\work\workitem\e\diagnostics.json'

Diff since the last good commit for rolling builds: 44a2b2d...45ed0ab which includes #93010 for which the PR had a similar failure but the PR was merged on red.

cc @pavelsavara

Author: radical
Assignees: -
Labels:

arch-wasm, blocking-clean-ci, area-VM-meta-mono, Known Build Error
Milestone: -

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Oct 17, 2023
@radical
Copy link
Member Author

radical commented Oct 17, 2023

Failing tests:
https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-ff2f87fff88148febc/Workloads-Wasm.Build.Tests.WasmBuildAppTest/1/console.72391d22.log?helixlogtype=result
https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-ff2f87fff88148febc/Workloads-Wasm.Build.Tests.NativeLibraryTests/1/console.b119e0be.log?helixlogtype=result
https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-444fb3ba110e4eb2ae/Workloads-NoWebcil-Wasm.Build.Tests.MainWithArgsTests/1/console.94d3fa1c.log?helixlogtype=result
https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-75da9917927147d090/Workloads-NoWebcil-Wasm.Build.Tests.InvariantGlobalizationTests/1/console.d6422600.log?helixlogtype=result

@radical radical mentioned this issue Oct 17, 2023
Merged
@radical radical changed the title [wasm] WBT tests failing randomly missing test app output [wasm] WBT tests failing because of missing test app output Oct 17, 2023
@pavelsavara
Copy link
Member

I see I made bad merge in #93010 and it contains the logging changes which I believed I moved to #93472 🤦‍♂️

@pavelsavara pavelsavara self-assigned this Oct 17, 2023
This was referenced Oct 17, 2023
Merged
Closed
Merged
Merged
@radical
Copy link
Member Author

radical commented Oct 18, 2023 •
edited
Loading

This has been fixed by #93618 .

@radical radical closed this as completed Oct 18, 2023
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Oct 18, 2023
@radical radical removed the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Oct 18, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Nov 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pavelsavara pavelsavara

Labels
arch-wasm WebAssembly architecture area-VM-meta-mono Known Build Error Use this to report build issues in the .NET Helix tab
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@radical @pavelsavara