Closed
Bug 1822225
Opened 2 years ago
Closed 2 years ago
Always capture async stacks in a11y browser tests
Categories
(Core :: Disability Access APIs, task)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
113 Branch
| Tracking | Status | |
|---|---|---|
| firefox113 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
Details
Attachments
(1 file)
The tests in accessible/tests/browser make heavy use of async functions for assertions. By default, where async functions are involved, the stack doesn't include the place where the async function was called. This makes it very difficult to debug these tests because we can't see which assertion is actually failing. This is especially problematic in CI. Therefore, we always want async stacks despite the default.
|
Assignee | |
Comment 1•2 years ago
|
||
Pushed by jteh@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/392292776d8d
Always produce async JS stacks in a11y browser tests. r=eeejay
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox113:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•