Timeout in WasmTestOnBrowser-subtlecrypto-System.Security.Cryptography.Tests

[karelz]

Test suite WasmTestOnBrowser-subtlecrypto-System.Security.Cryptography.Tests started timing out recently -- with first failure on 8/4

• 8/11 - last 120 days shows 27x failures (2x in Rolling runs) only on wasm

Example of failure:
Roolling run 1935076 on 8/10 PM - Console log

===========================================================================================================
/datadisks/disk1/work/BF5F09FE/w/AB0E099A/e /datadisks/disk1/work/BF5F09FE/w/AB0E099A/e /datadisks/disk1/work/BF5F09FE/w/AB0E099A/e
[1.0.0-prerelease.22375.5+d43453b9981bfd8705025250caff58d18e2abc7e] XHarness command issued: wasm test-browser --app=. --output-directory=/datadisks/disk1/work/BF5F09FE/w/AB0E099A/uploads/xharness-output -s dotnet.js.symbols --symbol-patterns wasm-symbol-patterns.txt --symbolicator WasmSymbolicator.dll,Microsoft.WebAssembly.Internal.SymbolicatorWrapperForXHarness --web-server-use-cop -- --setenv=TEST_EXPECT_SUBTLE_CRYPTO=true --run WasmTestRunner.dll System.Security.Cryptography.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[21:02:19] 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 39527
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
[21:02:19] info: Incoming arguments: --setenv=TEST_EXPECT_SUBTLE_CRYPTO=true --run WasmTestRunner.dll System.Security.Cryptography.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[21:02:19] info: Application arguments: --run WasmTestRunner.dll System.Security.Cryptography.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[21:02:20] info: browser: Console websocket connected.
[21:02:22] info: Initializing.....
[21:02:22] info: Discovering: System.Security.Cryptography.Tests.dll (method display = ClassAndMethod, method display options = None)
[21:02:25] info: Discovered:  System.Security.Cryptography.Tests.dll (found 1072 of 2624 test cases)
[21:02:25] info: Using random seed for test cases: 1992312536
[21:02:25] info: Using random seed for collections: 1992312536
[21:02:25] info: Starting:    System.Security.Cryptography.Tests.dll
[21:17:19] fail: Tests timed out. Killing driver service pid 21351
[21:17:19] fail: Application has finished with exit code TIMED_OUT but 0 was expected

[ghost]

Tagging subscribers to this area: @dotnet/area-system-security, @vcsjones
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Test suite WasmTestOnBrowser-subtlecrypto-System.Security.Cryptography.Tests started timing out recently -- with first failure on 8/4

• 8/11 - last 120 days shows 27x failures (2x in Rolling runs)

Example of failure:
Roolling run 1935076 on 8/10 PM - Console log

===========================================================================================================
/datadisks/disk1/work/BF5F09FE/w/AB0E099A/e /datadisks/disk1/work/BF5F09FE/w/AB0E099A/e /datadisks/disk1/work/BF5F09FE/w/AB0E099A/e
[1.0.0-prerelease.22375.5+d43453b9981bfd8705025250caff58d18e2abc7e] XHarness command issued: wasm test-browser --app=. --output-directory=/datadisks/disk1/work/BF5F09FE/w/AB0E099A/uploads/xharness-output -s dotnet.js.symbols --symbol-patterns wasm-symbol-patterns.txt --symbolicator WasmSymbolicator.dll,Microsoft.WebAssembly.Internal.SymbolicatorWrapperForXHarness --web-server-use-cop -- --setenv=TEST_EXPECT_SUBTLE_CRYPTO=true --run WasmTestRunner.dll System.Security.Cryptography.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[21:02:19] 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 39527
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
[21:02:19] info: Incoming arguments: --setenv=TEST_EXPECT_SUBTLE_CRYPTO=true --run WasmTestRunner.dll System.Security.Cryptography.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[21:02:19] info: Application arguments: --run WasmTestRunner.dll System.Security.Cryptography.Tests.dll -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
[21:02:20] info: browser: Console websocket connected.
[21:02:22] info: Initializing.....
[21:02:22] info: Discovering: System.Security.Cryptography.Tests.dll (method display = ClassAndMethod, method display options = None)
[21:02:25] info: Discovered:  System.Security.Cryptography.Tests.dll (found 1072 of 2624 test cases)
[21:02:25] info: Using random seed for test cases: 1992312536
[21:02:25] info: Using random seed for collections: 1992312536
[21:02:25] info: Starting:    System.Security.Cryptography.Tests.dll
[21:17:19] fail: Tests timed out. Killing driver service pid 21351
[21:17:19] fail: Application has finished with exit code TIMED_OUT but 0 was expected

Author:	karelz
Assignees:	-
Labels:	arch-wasm, area-System.Security, blocking-clean-ci
Milestone:	-

[karelz]

Given the high impact on CI (4x per day), can someone please take a look ASAP? Thanks!

[pavelsavara]

Should be fixed by #73537 please re-open if you see it after merge from main. Many thanks.