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:06, 29 October 2025

515 bytes removed ,  29 October 2025
remove adb failures section, rarely or not relevant
m (fixed ordering of paragraphs)
(remove adb failures section, rarely or not relevant)
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>
==About ADB failures on Android==
adb is a program which allows an external computer to control a phone, install software etc.
ADBTimeoutError: The command didn't finish for an unknown reason, e.g. a connection issue.
ADBError, ADBProcessError: Here one of the command the phone shall run failed. Each of the failures needs an own bug. E.g.
Intermittent raise ADBError("ADBDevice.__init__: ls could not be found")
means the program "ls" was not found. If it were a different program, a new bug should be filed.


==TV (test-verify) failure to test suite mapping==
==TV (test-verify) failure to test suite mapping==
Archaeopteryx
Confirmed users
613

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1255513"

Navigation menu