Issue metadata
Sign in to add a comment
|
64.5% regression in browser_tests at 501674:501686 |
||||||||||||||||||||
Issue descriptionoprypin@, do you have any insights into this test? The regression is only on Mac. Win7 and Linux are both still on 3.5 MOS.
,
Sep 15 2017
I haven't worked with this test at all
,
Sep 15 2017
Uh oh, that means that WebRTC is outputting almost pure noise on Mac! It's on the FYI bot, which means a WebRTC change could be suspect, but the WebRTC hash doesn't appear to change. Next step is to compare against the pure chromium bots...
,
Sep 15 2017
Both changes come in at the same time, so it's not because of a webrtc.org change... https://chromeperf.appspot.com/report?sid=3b750bbd5c93f87267ebee85bd3674a8e0403e417497bc13eb48a90a768b1bd8
,
Sep 15 2017
No obvious culprits in the changelogs (I looked for "audio", "webrtc", "mac").
,
Sep 15 2017
The FYI bot and regular bot are different machines (build107-b1 and build108-b1), so it seems very unlikely to be a machine error or config error.
,
Sep 15 2017
The errors happen on the same bot, so it's not due to a machine switch...
,
Sep 15 2017
I tried downloading a recent enough canary and WebRTC audio doesn not seem to be completely broken as the test would indicate. I can't find anything that could explain this. It's not urgent so therefore downgrading priority. I guess I'll have to build the test on mac and see if we can get it working again...
,
Sep 22 2017
The test works just fine locally, audio is loud and clear, so I guess something is wrong with this particular bot.
,
Sep 25 2017
Or bots, actually, since it hit both bots at the same time.
,
Oct 2 2017
Managed to log into the bot now and it's correctly configured.
,
Oct 2 2017
henrik reports the machine is 3,5 yrs old.
,
Oct 11 2017
All graphs have recovered, for some reason. I'm marking this as fixed.
,
Oct 11 2017
That's good news, but also very annoying. I really don't understand what happened here. Edward, did you do anything to the chromium FYI bots on Oct 2?
,
Oct 11 2017
Nope
,
Oct 11 2017
I agree it's annoying. I would estimate that a solid majority of the perf issues I triage end up in the "inexplicable" bucket. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 15 2017