If a bot loses connection to its devices Sheriff-o-Matic spams out lots of issues for the same bot |
||
Issue descriptionProblem with Sheriff-o-Matic For the following build https://uberchromegw.corp.google.com/i/internal.client.clank/builders/release-phone/builds/1125 Sheriff-o-Matic spammed me for every test stage that failed, in normal cases where there are different reasons for the different failures this is great, but in this case, where all the tests were failing because of the same issue (disconnected devices, see log trace below), Sheriff-o-Matic spammed me unnecessarily. I understand that it is probably super difficult to detect what went wrong for a certain build step so I'm not really expecting this bug to be fixed :/ but if you have any suggestions on how to make this less annoying that would be appreciated (maybe see some kinds of failures, such as devices not being connected, as build-stopping or something). E 0.015s Main Error occurred. Traceback (most recent call last): File "/b/build/slave/release-phone/build/src/build/android/test_runner.py", line 978, in main return RunTestsCommand(args) File "/b/build/slave/release-phone/build/src/build/android/test_runner.py", line 805, in RunTestsCommand return RunTestsInPlatformMode(args) File "/b/build/slave/release-phone/build/src/build/android/test_runner.py", line 846, in RunTestsInPlatformMode with environment_factory.CreateEnvironment(args, infra_error) as env: File "/b/build/slave/release-phone/build/src/build/android/pylib/base/environment.py", line 29, in __enter__ self.SetUp() File "/b/build/slave/release-phone/build/src/build/android/pylib/local/device/local_device_environment.py", line 65, in SetUp raise device_errors.NoDevicesError NoDevicesError: No devices attached.
,
Jul 8 2016
Ah cool, thanks! :)
,
Jul 26 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by seanmccullough@google.com
, Jul 8 2016