Confirmed users
571
edits
Sheriffing/How To/Intermittent bugs: Difference between revisions
add info about Test-Verify: how to find the original test suite
(→Manually filing a bug: add info about adb failures) |
(add info about Test-Verify: how to find the original test suite) |
||
| Line 5: | Line 5: | ||
[[File:Treeherder suggestion.png|Treeherder suggestions]] | [[File:Treeherder suggestion.png|Treeherder suggestions]] | ||
==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== | |||
The Test-Verify job tests if added or modified test files fail and runs them often sequential and in parallel in one or more sessions. To check if they also fail in their normal test suite, the test suite has to be identified. Search the log for the TV job for the test name and find e.g. | |||
<code>Per-test run found test toolkit/mozapps/extensions/test/browser/browser_webapi_access.js (mochitest-browser-chrome/None)</code> | |||
The test belongs to mochitest browser-chrome - the <code>bc</code> tasks on Treeherder. | |||
= Check for intermittency = | = Check for intermittency = | ||
| Line 76: | Line 94: | ||
Treeherder syncs with Bugzilla several times a day. Once your bug is added and the systems sync, Treeherder will suggest your new bug as a match for the next intermittent failure of this type. | Treeherder syncs with Bugzilla several times a day. Once your bug is added and the systems sync, Treeherder will suggest your new bug as a match for the next intermittent failure of this type. | ||
== Machine-specific failures == | == Machine-specific failures == | ||