Closed
Bug 1459927
Opened 7 years ago
Closed 7 years ago
The browser-chrome test harness doesn't always traverse async stack callers
Categories
(Testing :: Mochitest, enhancement, P1)
Testing
Mochitest
Tracking
(firefox62 fixed)
RESOLVED
FIXED
mozilla62
| Tracking | Status | |
|---|---|---|
| firefox62 | --- | fixed |
People
(Reporter: Paolo, Assigned: Paolo)
References
Details
Attachments
(1 file)
There is at least one code path in the browser-chrome test harness that doesn't traverse async stack callers.
| Comment hidden (mozreview-request) |
|
Assignee | |
Comment 2•7 years ago
|
||
|
|
Assignee | |
Comment 3•7 years ago
|
||
Comment on attachment 8974024 [details]
Bug 1459927 - Traverse nsIStackFrame async callers when reporting browser-chrome test harness failures. .mielczarek
Adding Joel to the possible reviewers.
Attachment #8974024 -
Flags: review?(jmaher)
|
||
Comment 4•7 years ago
|
||
| mozreview-review | ||
Comment on attachment 8974024 [details]
Bug 1459927 - Traverse nsIStackFrame async callers when reporting browser-chrome test harness failures. .mielczarek
https://reviewboard.mozilla.org/r/242348/#review250650
this looks straightforward from my end.
Attachment #8974024 -
Flags: review?(jmaher) → review+
|
|
Assignee | |
Comment 5•7 years ago
|
||
Comment on attachment 8974024 [details]
Bug 1459927 - Traverse nsIStackFrame async callers when reporting browser-chrome test harness failures. .mielczarek
Thanks!
Attachment #8974024 -
Flags: review?(ted)
Pushed by paolo.mozmail@amadzone.org:
https://hg.mozilla.org/integration/mozilla-inbound/rev/7fa8db24a617
Traverse nsIStackFrame async callers when reporting browser-chrome test harness failures. r=jmaher
|
||
Comment 7•7 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in
before you can comment on or make changes to this bug.
Description
•