Confirmed users
613
edits
Sheriffing/How To/Intermittent bugs: Difference between revisions
Jump to navigation
Jump to search
Sheriffing/How To/Intermittent bugs (view source)
Revision as of 16:09, 29 October 2025
, 29 October 2025add handling of wpt backlog failures on autoland
(remove adb failures section, rarely or not relevant) |
(add handling of wpt backlog failures on autoland) |
||
| Line 7: | Line 7: | ||
If a test failure has a suggestion with the test name and "single tracking bug" appended, it should be used for the failure classification if the failure is expected to be intermittent. Example: <code>Intermittent devtools/client/aboutdebugging/test/browser/browser_aboutdebugging_addons_debug_popup.js | single tracking bug</code> | If a test failure has a suggestion with the test name and "single tracking bug" appended, it should be used for the failure classification if the failure is expected to be intermittent. Example: <code>Intermittent devtools/client/aboutdebugging/test/browser/browser_aboutdebugging_addons_debug_popup.js | single tracking bug</code> | ||
==wpt failures on autoland== | |||
Backlog tasks for web platform tests run on autoland but only on Linux debug. On mozilla-central, the opt versions runs for all three desktop operating systems. If a permanent unexpected result is noticed and shall be handled with an update to the test expectation, the other "wpt" backlog tasks (= 1-2 per platform) shall be requested first to check if more platforms than Linux need to be updated. | |||
==TV (test-verify) failure to test suite mapping== | ==TV (test-verify) failure to test suite mapping== | ||