Closed Bug 1661320 Opened 5 years ago Closed 5 years ago

Intermittent Windows 10 Fis TEST-UNEXPECTED-TIMEOUT | /html/rendering/the-details-element/[details-page-break-after-1-print.html or details-page-break-before-2-print].html | expected PASS

Categories

(Core :: Printing: Setup, defect, P5)

x86_64
Windows 10
defect

Tracking

()

RESOLVED DUPLICATE of bug 1661138

People

(Reporter: intermittent-bug-filer, Assigned: emilio)

References

Details

(Keywords: intermittent-failure)

Filed by: nbeleuzu [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=314105853&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/dfKd26xsRcq54p1iRftoTg/runs/0/artifacts/public/logs/live_backing.log
Reftest URL: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/dfKd26xsRcq54p1iRftoTg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1


[task 2020-08-26T18:03:42.856Z] 18:03:42 INFO - TEST-START | /html/rendering/the-details-element/details-page-break-after-1-print.html
[task 2020-08-26T18:03:42.948Z] 18:03:42 INFO - PID 7972 | 1598465022939 Marionette INFO Testing http://web-platform.test:8000/html/rendering/the-details-element/details-page-break-after-1-print.html == http://web-platform.test:8000/html/rendering/the-details-element/details-two-pages-print-ref.html
[task 2020-08-26T18:03:56.127Z] 18:03:56 INFO - PID 7972 | [GFX1-]: Killing GPU process due to IPC reply timeout
[task 2020-08-26T18:03:57.222Z] 18:03:57 INFO - PID 7972 | ###!!! [Parent][MessageChannel::SendAndWait] Error: Channel error: cannot send/recv
[task 2020-08-26T18:03:57.222Z] 18:03:57 INFO - PID 7972 | [GFX1-]: Receive IPC close wit[GFX1-]: Receive IPC clhose with reason=AbnormalShutdo[wn Gr
[task 2020-08-26T18:03:57.222Z] 18:03:57 INFO - PID 7972 | FX1-]: Receiveeason=Abn[ormaGlSh utdIPCF clX1-]:ow n
[task 2020-08-26T18:03:57.223Z] 18:03:57 INFO - PID 7972 | Receive IPC close with reason=AbnormalShutdown
[task 2020-08-26T18:03:57.223Z] 18:03:57 INFO - PID 7972 | [GFX1-]: Receive IPC close with reason=AbnormalShutdown
[task 2020-08-26T18:03:57.223Z] 18:03:57 INFO - PID 7972 | ose with reason=AbnormalShutdown
[task 2020-08-26T18:03:57.223Z] 18:03:57 INFO - PID 7972 | [GFX1-]: Receive IPC close with reason=AbnormalShutdown
[task 2020-08-26T18:03:57.223Z] 18:03:57 INFO - PID 7972 | [GFX1-]: Receive IPC close with reason=AbnormalShutdown
[task 2020-08-26T18:03:57.228Z] 18:03:57 INFO - PID 7972 | [GFX1-]: IPC Channel is already torn down unexpectedly
[task 2020-08-26T18:03:57.228Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][MessageChannel] Error: (msgtype=0xB50006,name=PWebRenderBridge::Msg_SetDisplayList) Channel error: cannot send/recv
[task 2020-08-26T18:03:57.229Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][MessageChannel] Error: (msgtype=0xB50008,name=PWebRenderBridge::Msg_SetFocusTarget) Channel error: cannot send/recv
[task 2020-08-26T18:03:57.229Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][RunMessage] Error: Channel error: cannot send/recv
[task 2020-08-26T18:03:57.230Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][RunMessage] Error: Channel error: cannot send/recv
[task 2020-08-26T18:03:57.230Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][RunMessage] Error: Channel error: cannot send/recv
[task 2020-08-26T18:03:57.230Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][RunMessage] Error: Channel error: cannot send/recv
[task 2020-08-26T18:03:57.230Z] 18:03:57 INFO - PID 7972 | ###!!! [Parent][MessageChannel] Error: (msgtype=0x530014,name=PGPU::Msg_RemoveLayerTreeIdMapping) Channel error: cannot send/recv
[task 2020-08-26T18:03:57.240Z] 18:03:57 INFO - PID 7972 | ###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
[task 2020-08-26T18:03:57.240Z] 18:03:57 INFO - PID 7972 | ###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
[task 2020-08-26T18:03:57.240Z] 18:03:57 INFO - PID 7972 | ###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
[task 2020-08-26T18:03:57.245Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][MessageChannel] Error: (msgtype=0x36000C,name=PCompositorBridge::Msg___delete__) Channel error: cannot send/recv
[task 2020-08-26T18:03:57.245Z] 18:03:57 INFO - PID 7972 | [Parent 3540, Main Thread] WARNING: base::KillProcess refusing to terminate process handle 0: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_win.cc, line 401
[task 2020-08-26T18:03:57.245Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][MessageChannel] Error: (msgtype=0xB50025,name=PWebRenderBridge::Msg_Shutdown) Channel error: cannot send/recv
[task 2020-08-26T18:03:57.245Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][MessageChannel] Error: (msgtype=0xA10003,name=PTexture::Msg_Destroy) Channel error: cannot send/recv
[task 2020-08-26T18:03:57.245Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][MessageChannel] Error: (msgtype=0xA10003,name=PTexture::Msg_Destroy) Channel error: cannot send/recv
[task 2020-08-26T18:03:57.245Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][MessageChannel] Error: (msgtype=0xA10003,name=PTexture::Msg_Destroy) Channel error: cannot send/recv
[task 2020-08-26T18:03:57.246Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][MessageChannel] Error: (msgtype=0xD,name=PAPZ::Msg_Destroy) Channel error: cannot send/recv
[task 2020-08-26T18:03:57.246Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][MessageChannel] Error: (msgtype=0xB50025,name=PWebRenderBridge::Msg_Shutdown) Channel error: cannot send/recv
[task 2020-08-26T18:03:57.246Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][MessageChannel] Error: (msgtype=0xB50025,name=PWebRenderBridge::Msg_Shutdown) Channel error: cannot send/recv
[task 2020-08-26T18:03:57.246Z] 18:03:57 INFO - PID 7972 | ###!!! [Child][MessageChannel] Error: (msgtype=0xD,name=PAPZ::Msg_Destroy) Channel error: cannot send/recv
[task 2020-08-26T18:03:57.292Z] 18:03:57 INFO - PID 7972 | Can't find symbol 'eglSwapBuffersWithDamageEXT'.
[task 2020-08-26T18:03:57.292Z] 18:03:57 INFO - PID 7972 | [GFX1-]: Receive IPC close with reason=AbnormalShutdown
[task 2020-08-26T18:03:57.292Z] 18:03:57 INFO - PID 7972 | [GFX1-]: Receive IPC close with reason=AbnormalShutdown
[task 2020-08-26T18:03:57.292Z] 18:03:57 INFO - PID 7972 | [GFX1-]: Receive IPC close with reason=AbnormalShutdown
[task 2020-08-26T18:03:57.342Z] 18:03:57 INFO - TEST-UNEXPECTED-TIMEOUT | /html/rendering/the-details-element/details-page-break-after-1-print.html | expected PASS
[task 2020-08-26T18:03:57.342Z] 18:03:57 INFO - TEST-INFO took 14489ms
[task 2020-08-26T18:03:57.452Z] 18:03:57 INFO - PID 7972 | 1598465037445 Marionette INFO Stopped listening on port 50152
[task 2020-08-26T18:03:57.969Z] 18:03:57 INFO - Browser exited with return code 0
[task 2020-08-26T18:03:57.969Z] 18:03:57 INFO - PROCESS LEAKS None
[task 2020-08-26T18:03:57.969Z] 18:03:57 INFO - Closing logging queue
[task 2020-08-26T18:03:57.970Z] 18:03:57 INFO - queue closed
[task 2020-08-26T18:03:58.091Z] 18:03:58 INFO - Application command: Z:\task_1598464681\build\application\firefox\firefox.exe -marionette about:blank --wait-for-browser -profile c:\users\task_1598464681\appdata\local\temp\tmpydquas
[task 2020-08-26T18:03:58.091Z] 18:03:58 INFO - PID 11652 | Can't find symbol 'eglSwapBuffersWithDamageEXT'.
[task 2020-08-26T18:03:58.091Z] 18:03:58 INFO - PID 11652 | console.error: SearchCache: "_readCacheFile: Error reading cache file:" (new Error("", "(unknown module)"))
[task 2020-08-26T18:03:58.091Z] 18:03:58 INFO - PID 11652 | 1598465025253 Marionette INFO Listening on port 50198
[task 2020-08-26T18:03:58.091Z] 18:03:58 INFO - Starting runner

Flags: needinfo?(jfkthame)
Summary: Intermittent TEST-UNEXPECTED-TIMEOUT | /html/rendering/the-details-element/details-page-break-after-1-print.html | expected PASS → Intermittent TEST-UNEXPECTED-TIMEOUT | /html/rendering/the-details-element/details-page-break-[after-1-print]/[before-2-print].html | expected PASS

If I'm not wrong this looks like a hanging GPU process which gets killed after around 15s:

[task 2020-08-26T18:03:42.948Z] 18:03:42     INFO - PID 7972 | 1598465022939	Marionette	INFO	Testing http://web-platform.test:8000/html/rendering/the-details-element/details-page-break-after-1-print.html == http://web-platform.test:8000/html/rendering/the-details-element/details-two-pages-print-ref.html
[task 2020-08-26T18:03:56.127Z] 18:03:56     INFO - PID 7972 | [GFX1-]: Killing GPU process due to IPC reply timeout
[task 2020-08-26T18:03:57.222Z] 18:03:57     INFO - PID 7972 | ###!!! [Parent][MessageChannel::SendAndWait] Error: Channel error: cannot send/recv

Do we have retriggers for this?

This also looks to be Windows 10 Fission only.

Component: DOM: Core & HTML → Printing: Setup
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Summary: Intermittent TEST-UNEXPECTED-TIMEOUT | /html/rendering/the-details-element/details-page-break-[after-1-print]/[before-2-print].html | expected PASS → Intermittent Windows 10 Fis TEST-UNEXPECTED-TIMEOUT | /html/rendering/the-details-element/details-page-break-[after-1-print]/[before-2-print].html | expected PASS

Well I deserve that for asking ;)

Assignee: nobody → emilio
Flags: needinfo?(jfkthame)

Are the dumps or the crashes for this stuff somewhere? Otherwise it's not going to be easy to figure out...

Flags: needinfo?(hskupin)

(In reply to Emilio Cobos Álvarez (:emilio) from comment #7)

Are the dumps or the crashes for this stuff somewhere? Otherwise it's not going to be easy to figure out...

That's more a question for James. I don't know how wptrunner handles crashes or whatever happened here.

Flags: needinfo?(hskupin) → needinfo?(james)
Summary: Intermittent Windows 10 Fis TEST-UNEXPECTED-TIMEOUT | /html/rendering/the-details-element/details-page-break-[after-1-print]/[before-2-print].html | expected PASS → Intermittent Windows 10 Fis TEST-UNEXPECTED-TIMEOUT | /html/rendering/the-details-element/details-page-break-[after-1-print]/[before-2-print].html | details-page-break-after-2-print.html | expected PASS
Summary: Intermittent Windows 10 Fis TEST-UNEXPECTED-TIMEOUT | /html/rendering/the-details-element/details-page-break-[after-1-print]/[before-2-print].html | details-page-break-after-2-print.html | expected PASS → Intermittent Windows 10 Fis TEST-UNEXPECTED-TIMEOUT | /html/rendering/the-details-element/details-page-break-after-1-print.html or details-page-break-before-2-print].html | expected PASS
Summary: Intermittent Windows 10 Fis TEST-UNEXPECTED-TIMEOUT | /html/rendering/the-details-element/details-page-break-after-1-print.html or details-page-break-before-2-print].html | expected PASS → Intermittent Windows 10 Fis TEST-UNEXPECTED-TIMEOUT | /html/rendering/the-details-element/[details-page-break-after-1-print.html or details-page-break-before-2-print].html | expected PASS

Can't this be adjusted with an expectation patch?

I'm not sure this actually is a crash; it looks like we might be waiting 15s for the test to end and then killing the browser. But I'm not 100% sure. Given that there's no reftest-wait that would suggest either a bug in gecko or a bug in the harness. But if it regressed with Emilio's patch I'm going to claim maybe a bug in gecko ;)

Flags: needinfo?(james)

Could we manually help on finding out a regression range? If yes, could you please add more details for STR or a testcase?

QA Whiteboard: [qa-regression-triage]
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(emilio)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.