linux64-qr/debug crashtest perma-failing due to exceeding its max-run-time
Categories
(Testing :: General, defect)
Tracking
(firefox-esr68 unaffected, firefox71 unaffected, firefox72 unaffected, firefox73 fixed)
| Tracking | Status | |
|---|---|---|
| firefox-esr68 | --- | unaffected |
| firefox71 | --- | unaffected |
| firefox72 | --- | unaffected |
| firefox73 | --- | fixed |
People
(Reporter: gbrown, Assigned: kmag)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
linux64-qr/debug crashtests are exceeding the 60 minute max-run-time, as seen in bug 1411358.
https://treeherder.mozilla.org/logviewer.html#?job_id=281968125&repo=autoland
These tasks had been completing in ~25 minutes recently, so I am trying to find the regressing change.
|
Reporter | |
Comment 1•5 years ago
|
||
suggests this was regressed by bug 1588259.
It looks like non-qr debug crashtests also doubled in run-time around this change.
|
|
Reporter | |
Updated•5 years ago
|
|
Assignee | |
Comment 2•5 years ago
|
||
Oh... I think I know the problem. The test document added in that bug opens a copy of itself in a new window. And since the test file does a targetted form submission into the same window every time it loads, it probably just keeps doing that in the background until the end of the task.
I was expecting the crashtest harness to clean up any new windows or tabs at the end of the test, but I think I was expecting too much.
|
|
Assignee | |
Comment 3•5 years ago
|
||
Without this, the window just stays open in the background, constantly
re-submitting forms to itself.
Pushed by maglione.k@gmail.com: https://hg.mozilla.org/integration/autoland/rev/64ce7bbc34d4 Close window opened by crashtest after a brief timeout. r=smaug
|
||
Comment 5•5 years ago
|
||
| bugherder | ||
|
||
Updated•5 years ago
|
|
||
Updated•5 years ago
|
Description
•