It looks like we had a handful of failures in the same directory, most of them looking ~fuzzy but with one that's decidedly not-fuzzy: ``` skip-if(!browserIsRemote||!d2d||gpuProcess) == data:text/plain,FAIL about:blank ``` The reftest screenshot shows us rendering the `FAIL` text, with the reference case being blank. The comment in reftest.list adds some context about what that test is actually trying to do: https://searchfox.org/mozilla-central/rev/413b88689f3ca2a30b3c49465730c0e7d40f9188/layout/reftests/layers/reftest.list#33-40 Essentially the test is a "canary" which is never actually meant to be run (per its skip-if conditions); if conditions are such that it becomes enabled, it'll fail and be a signal for why other tests around it are failing, I think. In this case it looks like `gpuProcess` at least is false as shown at the start of the log -- and there are also some messages about the gpu process failing to spin up: ``` [task 2023-12-05T12:30:05.204Z] 12:30:05 INFO - [GFX1-]: Killing GPU process due to IPC reply timeout [task 2023-12-05T12:30:05.205Z] 12:30:05 INFO - [GFX1-]: Fallback WR to SW-WR + D3D11 [task 2023-12-05T12:30:05.205Z] 12:30:05 INFO - [GFX1-]: Failed to create remote compositor [task 2023-12-05T12:30:05.208Z] 12:30:05 INFO - [Parent 9224, Main Thread] WARNING: base::KillProcess refusing to terminate process handle 0: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_win.cc:349 [task 2023-12-05T12:30:05.209Z] 12:30:05 INFO - [GFX1-]: [D3D11] failed to get compositor device. [task 2023-12-05T12:30:05.210Z] 12:30:05 INFO - [GFX1-]: Failed to initialize CompositorD3D11 for SWGL: FEATURE_FAILURE_D3D11_NO_DEVICE [...] [task 2023-12-05T12:31:42.298Z] 12:31:42 INFO - REFTEST INFO | Dumping representation of sandbox which can be used for expectation annotations [...] [task 2023-12-05T12:31:42.309Z] 12:31:42 INFO - REFTEST INFO | gpuProcess: false ``` So it looks like this is a task that was meant to be a WebRender task (per `qr` in the name) but hardware webrender (and the gpu process) failed for some reason, and so there are some expected failures/fuzziness as a result.
Bug 1868357 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
It looks like we had a handful of failures in the same directory, most of them looking ~fuzzy but with one that's decidedly not-fuzzy: ``` skip-if(!browserIsRemote||!d2d||gpuProcess) == data:text/plain,FAIL about:blank ``` The reftest screenshot shows us rendering the `FAIL` text, with the reference case being blank. The comment in reftest.list adds some context about what that test is actually trying to do: https://searchfox.org/mozilla-central/rev/413b88689f3ca2a30b3c49465730c0e7d40f9188/layout/reftests/layers/reftest.list#33-40 Essentially the test is a "canary" which is never actually meant to be run (per its skip-if conditions); if conditions are such that it becomes enabled, it'll fail and be a signal for why other tests around it are failing, I think. In this case it looks like `gpuProcess` at least is false as shown at the start of the log -- and there are also some messages about the gpu process failing to spin up: ``` [task 2023-12-05T12:30:05.204Z] 12:30:05 INFO - [GFX1-]: Killing GPU process due to IPC reply timeout [task 2023-12-05T12:30:05.205Z] 12:30:05 INFO - [GFX1-]: Fallback WR to SW-WR + D3D11 [task 2023-12-05T12:30:05.205Z] 12:30:05 INFO - [GFX1-]: Failed to create remote compositor [task 2023-12-05T12:30:05.208Z] 12:30:05 INFO - [Parent 9224, Main Thread] WARNING: base::KillProcess refusing to terminate process handle 0: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_win.cc:349 [task 2023-12-05T12:30:05.209Z] 12:30:05 INFO - [GFX1-]: [D3D11] failed to get compositor device. [task 2023-12-05T12:30:05.210Z] 12:30:05 INFO - [GFX1-]: Failed to initialize CompositorD3D11 for SWGL: FEATURE_FAILURE_D3D11_NO_DEVICE [...] [task 2023-12-05T12:31:42.298Z] 12:31:42 INFO - REFTEST INFO | Dumping representation of sandbox which can be used for expectation annotations [...] [task 2023-12-05T12:31:42.309Z] 12:31:42 INFO - REFTEST INFO | gpuProcess: false ``` So it looks like this is a task that was meant to be a WebRender task (per `qr` in the name) but hardware webrender (and the gpu process) failed for some reason, and so there are some expected failures/fuzziness as a result.