New issue
Advanced search Search tips

Issue 863395 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: ----



Sign in to add a comment

tracing_perftests failing on chromium.perf/Android One Perf

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Jul 13

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of altimin@google.com

tracing_perftests failing on chromium.perf/Android One Perf

Builders failed on: 
- Android One Perf: 
  https://ci.chromium.org/buildbot/chromium.perf/Android%20One%20Perf


 
Mergedinto: 862106
Status: Duplicate (was: Available)
Marking this as a duplicate of bug 862106, as I'm seeing the same error message for both these bugs
Components: Infra>Labs
Labels: OS-Android
Status: Available (was: Duplicate)
This is not fixed with the fix to bug 862106.

Looks like device AG860440GIIE0GC is blacklisted, can labs team take a look?

Logs:
https://logs.chromium.org/v/?Curres=chrome%2Fbb%2Fchromium.perf%2FAndroid_One_Perf%2F1846%2F%2B%2Frecipes%2Fsteps%2Ftracing_perftests_on_Android_device_Android_One%2F0%2Fstdout

E   24.172s list_tests(AG860440GIIE0GC)  Shard failed: list_tests(AG860440GIIE0GC)
Traceback (most recent call last):
  File "/b/swarming/w/ir/build/android/pylib/local/device/local_device_environment.py", line 66, in wrapper
    return f(dev, *args, **kwargs)
  File "/b/swarming/w/ir/build/android/pylib/local/device/local_device_gtest_run.py", line 409, in list_tests
    device=dev)
  File "/b/swarming/w/ir/third_party/catapult/devil/devil/android/crash_handler.py", line 32, in RetryOnSystemCrash
    return f(device)
  File "/b/swarming/w/ir/build/android/pylib/local/device/local_device_gtest_run.py", line 408, in <lambda>
    None, d, flags=' '.join(flags), timeout=timeout),
  File "/b/swarming/w/ir/build/android/pylib/local/device/local_device_gtest_run.py", line 201, in Run
    stdout_file.name, device.StatPath(stdout_file.name).get('st_size', 0))
  File "/b/swarming/w/ir/third_party/catapult/devil/devil/android/device_utils.py", line 2046, in StatPath
    'Cannot find file or directory: %r' % device_path, str(self))
CommandFailedError: (device: AG860440GIIE0GC) Cannot find file or directory: '/storage/sdcard0/temp_file-f36b8f18cb565.gtest_out'
I   24.172s TimeoutThread-1-for-delete_temporary_file(AG860440GIIE0GC)  [host]> /b/swarming/w/ir/third_party/android_tools/sdk/platform-tools/adb -s AG860440GIIE0GC shell 'rm -f /data/local/tmp/temp_file-dc017b7d0e01b'
E   24.172s list_tests(AG860440GIIE0GC)  Device AG860440GIIE0GC blacklisted: list_tests
What's the hostname of the bot that has the device AG860440GIIE0GC?
Owner: vhang@chromium.org
Status: Fixed (was: Available)
Thanks to bev, she told me the device with serial number AG860440GIIE0GC is attached to build193-b7.  I've rebooted the device and it looks healthy.
Status: Assigned (was: Fixed)
Something is still wrong, seeing this on the latest run:
https://logs.chromium.org/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_One_Perf%2F1853%2F%2B%2Frecipes%2Fsteps%2Ftracing_perftests_on_Android_device_Android_One%2F0%2Fstdout

E   15.216s individual_device_set_up(AG860440GIIE0GC)  Device AG860440GIIE0GC blacklisted: individual_device_set_up
Labels: Infra-Troopers
Status: Untriaged (was: Assigned)
This same device seems to be still busted[1]:

  command: sh /data/local/tmp/temp_file-d5fcc9b797369.sh
  exit status: 255
  output:
  - mkdir failed for /storage/sdcard0/chromium_tests_root/, Read-only file system

[1] https://chrome-swarming.appspot.com/task?id=3f0cd231eba0e910&refresh=10&show_raw=1
Cc: vhang@chromium.org
Owner: ----
This is still failing. Waiting for a response from the troopers.
Components: Infra>Client>Chrome
Owner: jbudorick@chromium.org
Status: Assigned (was: Untriaged)
#6, 7: note that bugs don't appear in the trooper queue unless they either don't have an owner or they're P0.

This likely needs something analogous to https://chromium-review.googlesource.com/c/catapult/+/1145592. In general, that RO file system issue isn't a trooper issue. It's in other stuff I own, though, so I can address it today.

Sign in to add a comment