Issue metadata
Sign in to add a comment
|
19.3% regression in media_perftests at 536224:536251 |
||||||||||||||||||||
Issue description
This trace looks like a valid alert regression (caveat: media_perftests have no ref trace).
Perhaps useful to investigating is that two other media_perftests' metrics *improved* in the same range as this alert's original range. Those improvements are convert_fifo_only on chromium-rel-win7-gpu-{ati,nvidia}: https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICQnN6eoQoM
,
Feb 15 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12d1a743840000
,
Feb 15 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/12d1a743840000
,
Feb 15 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14b11cc3840000
,
Feb 15 2018
#4 is across a wider range than #2 (extended earlier).
,
Feb 20 2018
Hmm. I'm not sure why #4 still hasn't completed. I'll try starting another shortly.
,
Feb 20 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14ef42f7840000
,
Feb 20 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/14ef42f7840000
,
Feb 20 2018
,
Feb 20 2018
I'll try an even wider bisect. It's really hard to tell without a ref trace.
,
Feb 20 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14e37c8f840000
,
Feb 20 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/14e37c8f840000
,
Feb 20 2018
Given no repro multiple times and with widened bisects, my best guess is this isn't a Chrome regression, rather a change in infra. Lack of ref trace (crbug 714812) makes it hard to verify this assumption further. Closing as no-repro. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 15 2018