Closed
Bug 1662037
Opened 5 years ago
Closed 5 years ago
fix-stacks fails with an error running fileid on CI
Categories
(Toolkit :: Crash Reporting, defect)
Toolkit
Crash Reporting
Tracking
()
RESOLVED
FIXED
82 Branch
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox-esr78 | --- | unaffected |
firefox80 | --- | unaffected |
firefox81 | --- | wontfix |
firefox82 | --- | fixed |
People
(Reporter: heycam, Assigned: glandium)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
In my debug linux64 try run, fix-stacks is failing to symbolicate stack traces:
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=314437765&repo=try&lineNumber=11773
The error is:
Initializing stack-fixing for the first stack frame, this may take a while...
fix-stacks error: failed to run `/builds/worker/workspace/build/tests/bin/fileid` for `/builds/worker/workspace/build/application/firefox/libxul.so`
Updated•5 years ago
|
Has Regression Range: --- → yes
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → mh+mozilla
Assignee | ||
Comment 1•5 years ago
|
||
Pushed by mh@glandium.org:
https://hg.mozilla.org/integration/autoland/rev/2766680ff190
Update fix-stacks to a version that does not need fileid. r=njn
Comment 3•5 years ago
|
||
Set release status flags based on info from the regressing bug 1657217
status-firefox80:
--- → unaffected
status-firefox81:
--- → affected
status-firefox82:
--- → affected
status-firefox-esr68:
--- → unaffected
status-firefox-esr78:
--- → unaffected
![]() |
||
Comment 4•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
Updated•5 years ago
|
Keywords: regression
Comment 5•5 years ago
|
||
The patch landed in nightly and beta is affected.
:glandium, is this bug important enough to require an uplift?
If not please set status_beta
to wontfix
.
For more information, please visit auto_nag documentation.
Flags: needinfo?(mh+mozilla)
Updated•5 years ago
|
Flags: needinfo?(mh+mozilla)
You need to log in
before you can comment on or make changes to this bug.
Description
•