Performance regression happened on linux-perf/system_health.common_desktop/load_games_lazors/cpu_time_percentage_avg around 4/22 |
||||||
Issue descriptionFiling this bug to see if it's bisectable.
,
Jun 21 2018
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/12243963240000 All of the runs failed. The most common error (20/20 runs) was: Exception: Shard indicators must be present for perf tests
,
Jun 21 2018
Emily, any idea what this error means? I'm trying to run a bisect on a regression that I think took place around 2 months ago. Wondering if it has anything to do with recent buildbot step refactorings or resharding.
,
Jun 21 2018
Note that this also seemed to happen on load_news_bbc: https://chromeperf.appspot.com/report?sid=e3f83d992d0d563d3cbe2bf3246f43b02b1d1d7744b2df5505df634256870be4&start_rev=550912&end_rev=561003
,
Jun 21 2018
Yes, it's related to the buildbot step refactorings: https://bugs.chromium.org/p/chromium/issues/detail?id=836037#c26 There were some fixes on the Chromium side. It will be possible in the near future to re-run the job with those fixes applied, but it's not working right now: https://bugs.chromium.org/p/chromium/issues/detail?id=850812
,
Jun 21 2018
,
Jun 21 2018
Makes sense. I'll snooze this bug and stay posted.
,
Aug 2
,
Aug 6
Marking this as WontFix - this was mostly to appease my own curiosity anyhow. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jun 21 2018