Issue metadata
Sign in to add a comment
|
Android Nexus9 Perf (3) several tests failing due to adb flake |
||||||||||||||||||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus9%20Perf%20%283%29/builds/855 Failing: v8.key_mobile_sites_smooth v8.key_mobile_sites_smooth.reference smoothness.key_mobile_sites_smooth.reference smoothness.tough_animated_image_cases smoothness.tough_animated_image_cases.reference Looks like a variety of non test related issues, might just be flaky in several ways. From the logs of the above tests: AdbCommandFailedError: (device: HT4CTJT04123) adb shell '( ps | grep -F org.chromium.chrome; echo "PIPESTATUS: ${PIPESTATUS[@]}" );echo %$?': failed with exit status 255 and output: - error: device 'HT4CTJT04123' not found File "/b/build/slave/Android_Nexus9_Perf__3_/build/src/build/android/pylib/constants/__init__.py", line 264, in CheckOutputDirectory raise Exception('Neither CHROMIUM_OUTPUT_DIR nor CHROMIUM_OUT_DIR ' Exception: Neither CHROMIUM_OUTPUT_DIR nor CHROMIUM_OUT_DIR has been set (INFO) 2016-03-11 02:33:37,001 cmd_helper._ValidateAndLogCommand:153 [host]> /b/build/slave/Android_Nexus9_Perf__3_/build/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s HT4CTJT04201 shell '( ps | grep surfaceflinger );echo %$?' [ FAILED ] gifs.html (8432 ms)
,
Mar 14 2016
This has been passing since https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus9%20Perf%20%283%29/builds/865 Having said that I noticed the following when checking on the battery state (I do this on all devices I check on). This is similar to what is seen on Android Nexus 9 Perf (2) in https://bugs.chromium.org/p/chromium/issues/detail?id=592616. It looks like Android Nexus 9 Perf (1) has been stable? All these 3 builders are using identical usb hub/cable configuration. At this point I would start swapping out usb cables? If you feel this should be handled as a dup. of 592616 please "make it so". btw, I performed a dumpsys battery reset on those two devices. Checking HT4CTJT04123... Current Battery Service state: (UPDATES STOPPED -- use 'reset' to restart) AC powered: false USB powered: false Checking HT4CTJT03484... Current Battery Service state: (UPDATES STOPPED -- use 'reset' to restart) AC powered: false USB powered: false
,
Apr 27 2016
,
Apr 29 2016
I *believe* this issue is fixed, from looking at the past hundred or so builds. Please reopen if this is not the case. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by sullivan@chromium.org
, Mar 11 2016