Closed
Bug 1646406
Opened 5 years ago
Closed 5 years ago
Distinguish more robustly between user errors and actual exceptions that we should report on in mach
Categories
(Firefox Build System :: Mach Core, task)
Firefox Build System
Mach Core
Tracking
(firefox81 fixed)
RESOLVED
FIXED
81 Branch
Tracking | Status | |
---|---|---|
firefox81 | --- | fixed |
People
(Reporter: rstewart, Assigned: rstewart)
References
Details
Attachments
(1 file)
No description provided.
Comment 1•5 years ago
|
||
It looks like we already have a bit of infrastructure in-place for differentiating between a script that unexpectedly broke (except Exception
) and a slightly-more-expected exception (except FailedCommandError
).
It's also worth noting that we have two high-level exception handlers:
Comment 2•5 years ago
|
||
Ricky and I discussed this a little bit in our one-to-one meeting today:
- We can create a new top-level
UserError
(or something similarly named) that, when handled, simply prints the message and exits without reporting the error to Sentry or printing the "mach busted" text - This error will be used to replace all cases where we to tell the user via an exception that "we can't proceed until <x> happens".
Assignee | ||
Comment 3•5 years ago
|
||
Add a new UserError
class which when thrown doesn't get reported to Sentry.
Pushed by rstewart@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/18d42084d135
Distinguish between user errors and actual reportable exceptions in `mach` r=mhentges,froydnj
Comment 5•5 years ago
|
||
Backed out along with Bug 1655529 - please see https://bugzilla.mozilla.org/show_bug.cgi?id=1655529#c3
Backout by ncsoregi@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c0e293063894
Backed out 2 changesets (bug 1646406, bug 1655529) for geckoview failures. CLOSED TREE
Pushed by rstewart@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2ae4af0ee490
Distinguish between user errors and actual reportable exceptions in `mach` r=mhentges,froydnj
![]() |
||
Comment 8•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox81:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 81 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•