Confirmed users
571
edits
Sheriffing/How To/Intermittent bugs: Difference between revisions
→Manually filing a bug: add info about adb failures
(→Manually filing a bug: use Firefox::Untriaged for new bugs if product and component unknown) |
(→Manually filing a bug: add info about adb failures) |
||
| Line 76: | Line 76: | ||
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. | ||
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. | |||
== Machine-specific failures == | == Machine-specific failures == | ||