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
When a test is failing on master, currently it will end up failing on all submitted patches too. We should instead mark the results as BLOCKED rather than PENDING in the series; the test can be triggered manually on the series that fixes the breakage.
This way: 1) we can make the "T" icon yellow instead of red; 2) we don't inundate the mailing list with failures; 3) we can easily search the affected patches and retrigger testing on them (with "blocked:testing" as a search term).
The text was updated successfully, but these errors were encountered:
True. So another possibility is to add a base_status to the testing result data, and use it to distinguish error (red) from warning (yellow) in the dashboard.
When a test is failing on master, currently it will end up failing on all submitted patches too. We should instead mark the results as BLOCKED rather than PENDING in the series; the test can be triggered manually on the series that fixes the breakage.
This way: 1) we can make the "T" icon yellow instead of red; 2) we don't inundate the mailing list with failures; 3) we can easily search the affected patches and retrigger testing on them (with "blocked:testing" as a search term).
The text was updated successfully, but these errors were encountered: