Report crashes during wdspec tests as TEST-UNEXPECTED-CRASH
Categories
(Testing :: web-platform-tests, enhancement, P1)
Tracking
(firefox118 fixed)
Tracking | Status | |
---|---|---|
firefox118 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
(Blocks 1 open bug, Regressed 1 open bug)
Details
(Whiteboard: [webdriver:m8], [wptsync upstream])
Attachments
(1 file)
As right now we do not correctly report crashes of Firefox which could happen during the execution of wdspec tests, and as such failing tests are wrongly classified because the crash details as determined by mozcrash aren't taken into account. This could lead to missing information about crashes (maybe top-crashes) for Firefox where we could help developers in reproduction and fixing.
As such we should consider to report crashes correctly. Here a try build which shows a forced crash of Firefox by loading about:crashparent
https://treeherder.mozilla.org/logviewer?job_id=426057078&repo=try&lineNumber=7466
The downside is that we won't further run remaining tests in that particular pytest file. Probably that is fine for now.
Assignee | ||
Comment 1•1 year ago
|
||
I've submitted a try build to see how it works for existing non-modified wdspec tests:
https://treeherder.mozilla.org/jobs?repo=try&revision=0f14c379ab4f415a5b7a07d8015717da90681b9c
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 2•1 year ago
|
||
Comment 5•1 year ago
|
||
Backed out for causing high frequency failures in Bug 1849416
Assignee | ||
Comment 7•1 year ago
•
|
||
All the failures here in crash_content_process.py
happened on LInux opt no fission builds. It should be marked as intermittent PASS / FAIL until the underlying issue has been fixed.
Comment 9•1 year ago
|
||
bugherder |
Description
•