Closed
Bug 1758617
Opened 4 years ago
Closed 4 years ago
Content crash during PGO run leads to task timeout
Categories
(Firefox Build System :: General, enhancement)
Firefox Build System
General
Tracking
(firefox100 fixed)
RESOLVED
FIXED
100 Branch
| Tracking | Status | |
|---|---|---|
| firefox100 | --- | fixed |
People
(Reporter: glandium, Assigned: glandium)
Details
Attachments
(1 file)
No description provided.
| Assignee | ||
Comment 1•4 years ago
|
||
The expected behavior during a PGO run is that a browser is started and
exited once, and then it is started again on a page that runs various
workloads and once finished, exits.
When workload happens to crash the content process, the browser is left
running indefinitely, until the taskcluster task itself times out. This
leaves us with no possibility of knowing what actually went wrong during
the run, which is about the worst thing that can happen.
With the browser shutting down on its own in case of crash, the harness
can find the minidumps and report the crash, which is more useful.
Pushed by mh@glandium.org:
https://hg.mozilla.org/integration/autoland/rev/992fb0f6343f
Make Firefox abort in case of content crash during PGO run. r=firefox-build-system-reviewers,mhentges
Comment 3•4 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox100:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•