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

[wasm-mt] WasmTestOnBrowser-System.Xml.XmlSchemaSet.Tests fail #74408

Closed
simonrozsival opened this issue Aug 23, 2022 · 1 comment · Fixed by #75124
Closed

[wasm-mt] WasmTestOnBrowser-System.Xml.XmlSchemaSet.Tests fail #74408

simonrozsival opened this issue Aug 23, 2022 · 1 comment · Fixed by #75124
Assignees
Labels
arch-wasm WebAssembly architecture area-System.Xml
Milestone

Comments

@simonrozsival
Copy link
Member

The WasmTestOnBrowser-System.Xml.XmlSchemaSet.Tests get stuck and timeout when multi-threading is enabled.

Console output:

[1.0.0-prerelease.22411.1+5ebf69650b9f7b4ecab485be840b3022420f7812] XHarness command issued: wasm test-browser --app=. --output-directory=/datadisks/disk1/work/B1F5094D/w/A06008F3/uploads/xharness-output --web-server-use-cop -s dotnet.js.symbols --symbol-patterns wasm-symbol-patterns.txt --symbolicator WasmSymbolicator.dll,Microsoft.WebAssembly.Internal.SymbolicatorWrapperForXHarness -- --run WasmTestRunner.dll System.Xml.XmlSchemaSet.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[14:42:20] info: Starting chromedriver with args: --headless --incognito --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-renderer-backgrounding --enable-features=NetworkService,NetworkServiceInProcess --allow-insecure-localhost --disable-breakpad --disable-component-extensions-with-background-pages --disable-dev-shm-usage --disable-extensions --disable-features=TranslateUI --disable-ipc-flooding-protection --force-color-profile=srgb --metrics-recording-only
Starting ChromeDriver 100.0.4896.0 (ecbece54737a3df72a99f07de4850663ea5a48d3-refs/heads/main@{#972765}) on port 42945
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
[14:42:21] info: Incoming arguments: --run WasmTestRunner.dll System.Xml.XmlSchemaSet.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[14:42:21] info: Application arguments: --run WasmTestRunner.dll System.Xml.XmlSchemaSet.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[14:42:21] info: browser: [main] Console websocket connected.
[14:42:22] info: http://127.0.0.1:33011/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[14:42:22] info: http://127.0.0.1:33011/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[14:42:22] info: http://127.0.0.1:33011/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[14:42:22] info: http://127.0.0.1:33011/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[14:42:24] info: Initializing.....
[14:42:25] info: Discovering: System.Xml.XmlSchemaSet.Tests.dll (method display = ClassAndMethod, method display options = None)
[14:42:25] info: Discovered:  System.Xml.XmlSchemaSet.Tests.dll (found 328 of 328 test cases)
[14:42:25] info: Using random seed for test cases: 6912646
[14:42:25] info: Using random seed for collections: 6912646
[14:42:25] info: Starting:    System.Xml.XmlSchemaSet.Tests.dll
[14:42:26] warn: Blocking on the main thread is very dangerous, see https://emscripten.org/docs/porting/pthreads.html#blocking-on-the-main-browser-thread
[14:57:21] fail: Tests timed out. Killing driver service pid 5055
[14:57:21] fail: Application has finished with exit code TIMED_OUT but 0 was expected
XHarness exit code: 71 (GENERAL_FAILURE)

Full output: WasmTestOnBrowser-System.Xml.XmlSchemaSet.Tests/console

@simonrozsival simonrozsival added arch-wasm WebAssembly architecture area-System.Xml labels Aug 23, 2022
@simonrozsival simonrozsival added this to the 8.0.0 milestone Aug 23, 2022
@ghost
Copy link

ghost commented Aug 23, 2022

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

Issue Details

The WasmTestOnBrowser-System.Xml.XmlSchemaSet.Tests get stuck and timeout when multi-threading is enabled.

Console output:

[1.0.0-prerelease.22411.1+5ebf69650b9f7b4ecab485be840b3022420f7812] XHarness command issued: wasm test-browser --app=. --output-directory=/datadisks/disk1/work/B1F5094D/w/A06008F3/uploads/xharness-output --web-server-use-cop -s dotnet.js.symbols --symbol-patterns wasm-symbol-patterns.txt --symbolicator WasmSymbolicator.dll,Microsoft.WebAssembly.Internal.SymbolicatorWrapperForXHarness -- --run WasmTestRunner.dll System.Xml.XmlSchemaSet.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[14:42:20] info: Starting chromedriver with args: --headless --incognito --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-renderer-backgrounding --enable-features=NetworkService,NetworkServiceInProcess --allow-insecure-localhost --disable-breakpad --disable-component-extensions-with-background-pages --disable-dev-shm-usage --disable-extensions --disable-features=TranslateUI --disable-ipc-flooding-protection --force-color-profile=srgb --metrics-recording-only
Starting ChromeDriver 100.0.4896.0 (ecbece54737a3df72a99f07de4850663ea5a48d3-refs/heads/main@{#972765}) on port 42945
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
[14:42:21] info: Incoming arguments: --run WasmTestRunner.dll System.Xml.XmlSchemaSet.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[14:42:21] info: Application arguments: --run WasmTestRunner.dll System.Xml.XmlSchemaSet.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[14:42:21] info: browser: [main] Console websocket connected.
[14:42:22] info: http://127.0.0.1:33011/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[14:42:22] info: http://127.0.0.1:33011/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[14:42:22] info: http://127.0.0.1:33011/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[14:42:22] info: http://127.0.0.1:33011/dotnet.js 4 MONO_WASM: worker initializing essential C exports and APIs
[14:42:24] info: Initializing.....
[14:42:25] info: Discovering: System.Xml.XmlSchemaSet.Tests.dll (method display = ClassAndMethod, method display options = None)
[14:42:25] info: Discovered:  System.Xml.XmlSchemaSet.Tests.dll (found 328 of 328 test cases)
[14:42:25] info: Using random seed for test cases: 6912646
[14:42:25] info: Using random seed for collections: 6912646
[14:42:25] info: Starting:    System.Xml.XmlSchemaSet.Tests.dll
[14:42:26] warn: Blocking on the main thread is very dangerous, see https://emscripten.org/docs/porting/pthreads.html#blocking-on-the-main-browser-thread
[14:57:21] fail: Tests timed out. Killing driver service pid 5055
[14:57:21] fail: Application has finished with exit code TIMED_OUT but 0 was expected
XHarness exit code: 71 (GENERAL_FAILURE)

Full output: WasmTestOnBrowser-System.Xml.XmlSchemaSet.Tests/console

Author: simonrozsival
Assignees: -
Labels:

arch-wasm, area-System.Xml

Milestone: 8.0.0

@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Sep 6, 2022
@simonrozsival simonrozsival self-assigned this Sep 6, 2022
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Sep 8, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Oct 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-System.Xml
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant