New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 851552 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 845510
Owner: ----
Closed: Jun 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: ----



Sign in to add a comment

Strange (spurious?) device failures on Nexus 5X webview perf, many of which are related to PseudoLockAcquisitionTimeout

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Jun 11 2018

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of charliea@chromium.org

Strange (spurious?) device failures on Nexus 5X webview perf

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

Ned, it looks like many of the blink_perf benchmarks on 5X webview perf seem to be failing flakily with cloud storage PseudoLockAcquisitionTimeouts. Here's a link to an example log: https://logs.chromium.org/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus5X_WebView_Perf%2F1971%2F%2B%2Frecipes%2Fsteps%2Fblink_perf.css_on_Android_device_Nexus_5X%2F0%2Fstdout

Any idea what might be going on here that these are failing all of a sudden?
 
I was looking into the flock errors in bug 845510. I'll try to get to that again soon.

Comment 2 by hzl@chromium.org, Jun 11 2018

Cc: bpastene@chromium.org

Comment 3 by hzl@chromium.org, Jun 11 2018

Mergedinto: 845510
Status: Duplicate (was: Available)
Actually I will just merge this issue with 845510 since they seem to have same stacktrace.

Sign in to add a comment