Bug 243063 – [ Merge-Queue ] http/tests/xmlhttprequest/connection-error-sync.html crashed possibly causing other tests to timeout

• Status: NEW
• Component: Page Loading

[Dawn Morningstar]

webgl/2.0.0/conformance2/textures/canvas/tex-2d-rgb565-rgb-unsigned_short_5_6_5.html is a flaky text failure

HISTORY:
https://results.webkit.org/?suite=layout-tests&test=webgl%2F2.0.0%2Fconformance2%2Ftextures%2Fcanvas%2Ftex-2d-rgb565-rgb-unsigned_short_5_6_5.html

This one is a Merge-Queue specific failure (Appears to be on Big Sur WK2) that only has:

#EOF

as it's stderr...
STDERR-URL:
https://ews-build.s3-us-west-2.amazonaws.com/Merge-Queue/454f1f66-1871/webgl/2.0.0/conformance2/textures/canvas/tex-2d-rgb565-rgb-unsigned_short_5_6_5-stderr.txt


Alexey's theory that parallelism might be too much for these Macs may be correct; but we really don't have a lot to go off of for this bug. Marking expectations to help merge queue.

[Dawn Morningstar]

Ah I mistyped this is actually a flaky timeout.

(In reply to Matteo Flores from comment #0)
> webgl/2.0.0/conformance2/textures/canvas/tex-2d-rgb565-rgb-
> unsigned_short_5_6_5.html is a flaky text failure

[Dawn Morningstar]

Changing the title of this bug; I now believe that http/tests/xmlhttprequest/connection-error-sync.html's crash is the cause of all the timeouts on this queue. Further, I cannot find another instance of this crash and I also searched the history for any of these tests as timeout on merge-queue and couldn't find any.

Test results: https://ews-build.s3-us-west-2.amazonaws.com/Merge-Queue/454f1f66-1871/results.html

I also believe that this crash is a one off newtwork process crash - I don't think expectations are the right way to proceed now after discovering these details.

[Radar WebKit Bug Importer]

<rdar://problem/97409287>