Closed
Bug 1893537
Opened 1 year ago
Closed 1 year ago
when a reftest fails store all modifiers and related manifest info in the errorsummary for unique test identification
Categories
(Testing :: Reftest, task)
Testing
Reftest
Tracking
(firefox127 fixed)
RESOLVED
FIXED
127 Branch
| Tracking | Status | |
|---|---|---|
| firefox127 | --- | fixed |
People
(Reporter: jmaher, Assigned: jmaher)
Details
Attachments
(1 file, 1 obsolete file)
currently now it is very difficult to figure out which test fails in a reftest manifest where the same test/ref are used but with different preferences or runtime modifications. This becomes even more difficult to create tools for auto sheriffing. Adding the info from the manifest will provide data.
|
Assignee | |
Comment 1•1 year ago
|
||
this will replace work done in bug 1892351
|
|
Assignee | |
Comment 2•1 year ago
|
||
|
||
Updated•1 year ago
|
Assignee: nobody → jmaher
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 3•1 year ago
|
||
|
|
||
Updated•1 year ago
|
Attachment #9398726 -
Attachment is obsolete: true
Pushed by jmaher@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f734b044add3
Add reftest modifiers to errorsummary upon failure. r=gbrown
|
||
Comment 5•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox127:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 127 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•