You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Run a whole-map live verification pass on demand and report what is new since the last pass - part 3 of 6 #16568
Part 3 of 6 of #15649, split at intake (owner Q93). The done-when below is copied from #15649 as written.
Done when
/testing:run-e2e map baseline=<findings.json> runs the compare script and opens its report with both pass builds, then NEW, PRE-EXISTING and GONE findings by severity with one summary line per group, ordered by the map_report_order setting.
/testing:run-e2e has settings file_findings (none default, new) and file_findings_floor (high default); under new it states the count, then hands each NEW finding at or above the floor to /bugs:write with its id in the report, and never closes a GONE one.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: this is part 3 of 6 of #15649. It asks /testing:run-e2e map baseline=<findings.json> to run the compare script and report NEW, PRE-EXISTING and GONE findings, ordered by map_report_order. It also asks for the file_findings and file_findings_floor settings, which hand NEW findings at or above the floor to /bugs:write and never close a GONE one. The done-when is exact, so nothing is missing. The sibling parts are #16566, #16567, #16569, #16570 and #16571. No merged pull request appears to fix this already.
Activity
github-actions commentedon Nov 16, 2026
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: this is part 3 of 6 of #15649. It asks
/testing:run-e2e map baseline=<findings.json>to run the compare script and report NEW, PRE-EXISTING and GONE findings, ordered bymap_report_order. It also asks for thefile_findingsandfile_findings_floorsettings, which hand NEW findings at or above the floor to/bugs:writeand never close a GONE one. The done-when is exact, so nothing is missing. The sibling parts are #16566, #16567, #16569, #16570 and #16571. No merged pull request appears to fix this already.Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 16, 2026
Not admitted to the issue lane yet: blocker #16567 is not closed by a listed human or a merge.