Issue metadata
Sign in to add a comment
|
mash_browser_tests flaky on the chromeos try bot |
||||||||||||||||||||||||
Issue descriptionThis seems to be flaking pretty often (maybe 1/8-1/4 of runs). The step fails without much of an error message. It is affecting the stability of the ANGLE CQ. Not sure if this is a recent regression or something long-standing. Seems to have been happening for a while. example fail: https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_ozone_rel_ng/builds/422286 More failures here: https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_ozone_rel_ng?numbuilds=200 Victor do you know a potential owner?
,
Jul 13 2017
This is still happening a lot -- from the title of 678687, it seems like that bug is not specifically about the flaky timeout failure of mash_browser_tests on linux_chromium_chromeos_ozone_rel_ng so I'll keep this bug separate for now. Example log: https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Ftryserver.chromium.linux%2Flinux_chromium_chromeos_ozone_rel_ng%2F428088%2F%2B%2Frecipes%2Fsteps%2Fmash_browser_tests__with_patch_%2F0%2Fstdout jonross@, do you know why mash_browser_tests is timing out on that builder and what we might try to do next to avoid this?
,
Jul 13 2017
Marking as P1 because frequent timeouts on try bots affect a lot of developers by increasing CQ false negatives and CQ time
,
Jul 13 2017
The flakes are caused by a race condition within Ash, when it is trying to access font. I'm merging this into the main bug tracking that problem. A fix has been submitted to the CQ: https://chromium-review.googlesource.com/c/568789/ |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ynovikov@chromium.org
, Jul 7 2017