XHarness message of order error leading to timeout

[jkoritzinsky]

Build

https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=925619

Build leg reported

WasmTestOnChrome-MT-System.Runtime.CompilerServices.Unsafe.Tests.WorkItemExecution

Pull Request

dotnet/runtime#111716

Known issue core information

Fill out the known issue JSON section by following the step by step documentation on how to create a known issue

 {
    "ErrorMessage" : "fail: [out of order message from the driver]: Unable to receive message from renderer",
    "BuildRetry": false,
    "ErrorPattern": "",
    "ExcludeConsoleLog": false
 }

@dotnet/dnceng

Release Note Category

• Feature changes/additions
• Bug fixes
• Internal Infrastructure Improvements

Release Note Description

Additional information about the issue reported

XHarness receives this message out of order, gets disconnected, and then keeps trying to reconnect until the job times out.

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=925619
Error message validated: [fail: [out of order message from the driver]: Unable to receive message from renderer]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 1/22/2025 10:48:35 PM UTC

Report

Build	Definition	Test	Pull Request
937397	dotnet/runtime	WasmTestOnChrome-ST-System.Runtime.Serialization.Primitives.Tests.WorkItemExecution
933488	dotnet/runtime	WasmTestOnChrome-ST-System.Runtime.InteropServices.RuntimeInformation.Tests.WorkItemExecution	dotnet/runtime#111953
925619	dotnet/runtime	WasmTestOnChrome-MT-System.Runtime.CompilerServices.Unsafe.Tests.WorkItemExecution	dotnet/runtime#111716

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	1	3

[dougbu]

not sure whether is is pervasive / broad enough to be a dotnet/dnceng issue

separately, DNCEng no longer manages the dotnet/xharness repo. I think @ivanpovazan and others who've done recent work may be able to help you

[ivanpovazan]

@ilonatommy @akoeplinger have you encountered this before?

[ilonatommy]

Yes, we used to hit it on the runtime dotnet/runtime#103061 and it was fixed by increasing the timeout for running these tests.

[ivanpovazan]

Thanks, is there a ticket to increase the timeout again?

[ilonatommy]

No, we stopped hitting it after the fix got merged

[ilonatommy]

@maraf, do you know if the issue got some other way of fixing? I can see that the timeout increase is removed already

[maraf]

No idea. Maybe we did some detection of browser crash?