Issue 841917 link

Starred by 2 users

Issue metadata

Status:	Assigned
Owner:	jbudorick@chromium.org
Cc:	charliea@chromium.org
EstimatedDays:	----
NextAction:	----
OS:	----
Pri:	1
Type:	----
Performance-Sheriff-BotHealth Filed-Via-SoM

devil causing benchmark failures due with PseudoLockAcquisitionTimeout

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, May 10 2018

Issue description

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

Example: https://logs.chromium.org/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus6_WebView_Perf%2F1743%2F%2B%2Frecipes%2Fsteps%2Fblink_perf.canvas_on_Android%2F0%2Fstdout

This has caused two consecutive failures on Nexus 6 Webview Perf/blink_perf.canvas:

- https://ci.chromium.org/buildbot/chromium.perf/Android%20Nexus6%20WebView%20Perf/1743
- https://ci.chromium.org/buildbot/chromium.perf/Android%20Nexus6%20WebView%20Perf/1744

Based on the callstack, it looks like this is going through devil.

Comment 1 by charliea@chromium.org, May 10 2018

Owner: jbudorick@chromium.org

jbudorick@, can you route this appropriately? Marked it as P1 because it's causing at least one benchmark to fail regularly on the waterfall. I'll add further comments if I find more failures to help prioritize this.

Comment 2 by charliea@chromium.org, May 10 2018

Looks like this is also causing failures on the last two runs of power.typical_10_mobile.

Comment 3 by benhenry@chromium.org, Aug 2

Status: Assigned (was: Available)

►

Issue 841917 link

Issue metadata

devil causing benchmark failures due with PseudoLockAcquisitionTimeout

Issue description

Comment 1 by charliea@chromium.org, May 10 2018

Comment 1 Deleted

Comment 2 by charliea@chromium.org, May 10 2018

Comment 2 Deleted

Comment 3 by benhenry@chromium.org, Aug 2

Comment 3 Deleted

Sign in to add a comment