source-test-doc-generate doesn't output the new warnings
Categories
(Developer Infrastructure :: Source Documentation, defect)
Tracking
(firefox134 fixed)
| Tracking | Status | |
|---|---|---|
| firefox134 | --- | fixed |
People
(Reporter: standard8, Assigned: standard8)
References
(Depends on 2 open bugs, Blocks 1 open bug)
Details
Attachments
(1 file)
In bug 1861953 we made it so that the "x new warnings" line was being reported on the treeherder summaries. However, we don't currently have a way of determining and displaying which warnings are the new ones.
Currently CI has about 809 warnings. That seems a little big for an allow list, so we might need to get that down first - bug 1817962 might help with this, as I'm only seeing 318 locally.
The other alternative would be some way to track what was in the previous CI run, but I would expect that we want this to be useful locally so that when a developer runs ./mach doc any new warnings are made clear there as well.
Comment 1•2 years ago
|
||
The severity field is not set for this bug.
:Sylvestre, could you have a look please?
For more information, please visit BugBot documentation.
Updated•2 years ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
The meta Bug 1878968 is tracking the work for reducing the warnings, as part of that we're also moving warnings to be "fatal" warnings - so for those ones any new errors will get output in the summary section at the bottom.
| Assignee | ||
Comment 4•1 year ago
|
||
This removes the separate handling of different types of warnings/failures, and switches to an allow list of warnings that are the existing ones. They'll still be output as TEST-KNOWN-FAIL. Any new warnings will be output as TEST-UNEXPECTED-FAIL and cause the document generation/upload to fail.
Depends on D225959
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 6•1 year ago
|
||
| bugherder | ||
Description
•