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

Issue 788772 link

Starred by 2 users
Status: Assigned
Owner:
vmi...@chromium.org
Cc:
█ nednguyen@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

smoothness.tough_texture_upload_cases failing on multiple builders

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Nov 27 2017 
smoothness.tough_texture_upload_cases failing on multiple builders

Builders failed on: 
- Android Nexus5X WebView Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20WebView%20Perf
- Android One Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf

Comment 1 by pkasting@chromium.org, Dec 7 2017

Cc: nednguyen@chromium.org
Labels: -Sheriff-Chromium Performance-Sheriff-BotHealth
Status: Untriaged (was: Available)
Looks like at this point only extra_large_texture_uploads.html is failing, and it's doing so rarely on the Nexus5X bot but frequently on the Android One bot.

I looked at some of the changelogs and did some bug searching but didn't see anything immediately obvious.  Maybe this is more appropriate for the perf bot health queue?  Not sure who should own this.  +CC nednguyen who seems knowledgeable about some of these types of failure messages (I dunno).

Comment 2 by nedngu...@google.com, Dec 7 2017

Owner: vmi...@chromium.org
Status: Assigned (was: Untriaged)
pkasting@: can you disable the test mean while?

Reassign to Victor, benchmark owner

Comment 3 by vmi...@chromium.org, Dec 7 2017 

Thanks, please disable if you can.  I am taking a look on Nexus5X.  This test is likely too slow to complete enough iterations to compute smoothness on these devices.
►

Sign in to add a comment