Closed Bug 1459927 Opened 6 years ago Closed 6 years ago

The browser-chrome test harness doesn't always traverse async stack callers

Categories

(Testing :: Mochitest, enhancement, P1)

Product:
Testing
Component:
Mochitest
Type:
enhancement

Tracking

(firefox62 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla62
Tracking Flags:
Tracking Status
firefox62 --- fixed

People

(Reporter: Paolo, Assigned: Paolo)

References

Details

Attachments

(1 file)

Bug 1459927 - Traverse nsIStackFrame async callers when reporting browser-chrome test harness failures. .mielczarek
59 bytes, text/x-review-board-request
jmaher
: review+
Details 
There is at least one code path in the browser-chrome test harness that doesn't traverse async stack callers.
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 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+
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
https://hg.mozilla.org/mozilla-central/rev/7fa8db24a617
Status: ASSIGNED → RESOLVED
Closed: 6 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.

Attachment

General

Creator:
Created:
Updated:
Size: