1513294 - Intermittent TEST-UNEXPECTED-CRASH | /wasm/serialization/broadcastchannel-success.html | list index out of range

Status: RESOLVED INCOMPLETE

(Core :: JavaScript: WebAssembly, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: ncsoregi [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=216383015&repo=autoland

https://queue.taskcluster.net/v1/task/UwidwioLQUm5jUwCKL6JPQ/runs/0/artifacts/public/logs/live_backing.log

16:41:43     INFO - PID 5584 | A content process crashed and MOZ_CRASHREPORTER_SHUTDOWN is set, shutting down
16:41:43     INFO - PID 5584 | [Parent 2272, Gecko_IOThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 327
16:41:43     INFO - PID 5584 | [Parent 2272, Gecko_IOThread] WARNING: file z:/build/build/src/ipc/chromium/src/base/process_util_win.cc, line 166
16:41:43     INFO - PID 5584 | [Child 5552, Chrome_ChildThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 327
16:41:43  WARNING - Traceback (most recent call last):
16:41:43  WARNING -   File "Z:\task_1544542475\build\tests\web-platform\tests\tools\wptrunner\wptrunner\executors\executormarionette.py", line 589, in _run
16:41:43  WARNING -     self.result = True, self.func(self.protocol, self.url, self.timeout)
16:41:43  WARNING -   File "Z:\task_1544542475\build\tests\web-platform\tests\tools\wptrunner\wptrunner\executors\executormarionette.py", line 701, in do_testharness
16:41:43  WARNING -     test_window = protocol.testharness.get_test_window(self.window_id, parent_window)
16:41:43  WARNING -   File "Z:\task_1544542475\build\tests\web-platform\tests\tools\wptrunner\wptrunner\executors\executormarionette.py", line 205, in get_test_window
16:41:43  WARNING -     elif after[0] == parent and len(after) > 2:
16:41:43  WARNING - IndexError: list index out of range
16:41:43  WARNING - 
16:41:43     INFO - mozcrash Downloading symbols from: https://queue.taskcluster.net/v1/task/QiK4HXv7SUObK8P13ahkLA/artifacts/public/build/target.crashreporter-symbols.zip
16:41:43     INFO - PID 5584 | [Parent 2272, Gecko_IOThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 327
16:41:43     INFO - PID 5584 | [Child 5972, Chrome_ChildThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 327
16:41:43     INFO - PID 5584 | [Parent 2272, Gecko_IOThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 327
16:41:43     INFO - PID 5584 | [Parent 2272, Gecko_IOThread] WARNING: file z:/build/build/src/ipc/chromium/src/base/process_util_win.cc, line 166
16:41:44     INFO - PID 5584 | 1544546504008	Marionette	INFO	Stopped listening on port 2828
16:41:46     INFO - mozcrash Copy/paste: Z:\task_1544542475\build\win32-minidump_stackwalk.exe c:\users\task_1544542475\appdata\local\temp\tmplygefo.mozrunner\minidumps\3f171746-471f-4f71-9c31-68789449f86c.dmp c:\users\task_1544542475\appdata\local\temp\tmpnfzopj
16:41:55     INFO - mozcrash Saved minidump as Z:\task_1544542475\build\blobber_upload_dir\3f171746-471f-4f71-9c31-68789449f86c.dmp
16:41:55     INFO - mozcrash Saved app info as Z:\task_1544542475\build\blobber_upload_dir\3f171746-471f-4f71-9c31-68789449f86c.extra
16:41:55     INFO - TEST-UNEXPECTED-CRASH | /wasm/serialization/broadcastchannel-success.html | list index out of range
16:41:55     INFO - TEST-INFO took 12125ms
16:41:55     INFO - Browser exited with retur

Comment 1

[Luke Wagner [:luke]]

Joel: do you happen to know if there is a way to get crash stacks for wpt TEST-UNEXPECTED-CRASHes?

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

for this one, you can look on treeherder, click on the job and view the artifacts:
https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=e5c12de36d68973123a187810485cc2fae6344c2&selectedJob=216383015

doing this yields the .dmp and .extra file.  Are you looking for wpt to run minidump stackwalk and dump info into the log?

Comment 3

[Luke Wagner [:luke]]

Ah, great to know that .dmp files are uploaded as artifacts.  But yes, I was hoping the stack could be printed into the log.  That seems to be the case for some/many of the test logs and it's really helpful and time-saving; I'd love it if all tests did this automatically.

Comment 4

[Joel Maher ( :jmaher ) (UTC -8)]

:jgraham, do you know if wpt runs minidump stackwalk and prints the output in the log file?

Comment 5

[James Graham [:jgraham]]

It's definitely *supposed* to. It looks like we're reading the dump file since we see [1] which comes from [2]. We actually call into mozcrash twice, once to run check_for_crashes() and once to run log_crash(). I think that's the problem, because after the first call the files are being moved. If that *is* the problem, I'm astonished it hasn't come up before (and I'm sure I've seen this work before, so…). Anyway I'll try chaging it so that when we are just looking for crashes we don't touch the files.

[1] https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=216383015&repo=autoland&lineNumber=8352
[2] https://searchfox.org/mozilla-central/source/testing/mozbase/mozcrash/mozcrash/mozcrash.py#253

Comment 6

[Intermittent Failures Robot]

2 failures in 2485 pushes (0.001 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:
* autoland: 1
* mozilla-central: 1

Platform breakdown:
* windows7-32: 2

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1513294&startday=2018-12-10&endday=2018-12-16&tree=all

Comment 7

[Firefox Bug Husbandry Bot]

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup