clicking on graph button no longer brings up a graph with reference build results |
||
Issue descriptionNow the result only has the test build results. This means sheriffs have to take extra steps to figure out if a regression is a device issue or a chrome issue. my sheriff dashboard like this: https://chromeperf.appspot.com/alerts?sheriff=Chromium%20Perf%20AV%20Sheriff&sortby=end_revision&sortdirection=down links me to a page like this: https://chromeperf.appspot.com/report?masters=ChromiumPerf&bots=chromium-rel-mac12&tests=media.desktop%2Fmemory%3Achrome%3Aall_processes%3Areported_by_chrome%3Agpu%3Aeffective_size_avg%2Fvideo.html%3Fsrc_tulip2.vp9.webm_background&checked=video.html%3Fsrc_tulip2.vp9.webm_background%2Cvideo.html%3Fsrc_tulip2.vp9.webm_background_ref%2Cref&rev=555479 which doesn't show a reference build. This used to work, but I haven't been a sheriff in a while so I don't know when it used to work.
,
May 18 2018
It is still an issue, yes. I just repro'd it again.
,
May 18 2018
We can videochat so I can show you repro steps if you are available.
,
May 21 2018
,
May 23 2018
I can manually add the ref build, so the ref build is uploading data: https://chromeperf.appspot.com/report?sid=86e9633731458536fa35b44f2df02f122a13bbd0a87d9c8f03ce086a1b553eca It would probably take more time than it's worth to debug why the UI isn't automatically adding the ref build. Ref builds do load in the new version of the dashboard: https://v2spa-dot-chromeperf.appspot.com/#testSuite=media.desktop&measurement=story%253Apower&bot=ChromiumPerf%253Achromium-rel-mac11-pro Can you try using V2SPA to triage that rotation and let me know if there are any bugs or missing features that would prevent you from using it? https://v2spa-dot-chromeperf.appspot.com/#sheriff=Chromium_Perf_AV_Sheriff Known issues and status of the new UI: http://go/chromeperf-v2-status
,
May 23 2018
"Improvements" and "Triaged" buttons on the new UI don't see to work, so I can't see any alerts to try this on in the new UI. |
||
►
Sign in to add a comment |
||
Comment 1 by simonhatch@chromium.org
, May 18 2018