"Linux ChromiumOS Tests (dbg)(1)" in bad state |
||||||
Issue descriptionBuild is broken: browser_tests on Ubuntu-12.04 Revision range: chromium 406043 : 406054 Failing builders: Linux ChromiumOS Tests (dbg)(1): https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Tests%20(dbg)(1) It looks "Builder: Linux ChromiumOS Tests (dbg)(1)" has been failing (Exception steps exception browser_tests on ubuntu-12.04 failed interactive_ui_tests on ubuntu-12.04 failed unit_tests on ubuntu-12.04 failed failure reason ) from https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Tests%20%28dbg%29%281%29/builds/16297
,
Jul 22 2016
Issue 630612 has been merged into this issue.
,
Jul 22 2016
FYI, the nearly CCed folks are current sheriffs. (i.e., we're not the answer to "please cc anyone else who'd know how to investigate the tests.") I promise to look if I have time, but right now a lot of other things are causing more redness than this bot.
,
Jul 22 2016
Fundamentally, this bot is in a bad state. https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Tests%20%28dbg%29%281%29 We have the series of exceptions on July 20-21 that caused the filing of this bug. These went away for a while and have now returned. As sheriff, I'm not quite sure how seriously to take the new failures that appeared at the same time as the exceptions returned.
,
Jul 25 2016
This bot seems mostly fine now. Removing from sheriff-queue but leaving the bug open in case anyone (jam@ agable@) wants to investigate the earlier failures. Note that this bug had bug 630612 dupped into it. That bug covers its insanely long pending build queue, which is still an issue.
,
Jul 25 2016
Issue 630833 has been merged into this issue.
,
Jul 25 2016
Basically, this bot got slow. This has caused a big pending queue, and has caused it to be building old revisions which, while correct, is confusing. I'm going to nuke its checkout, clear its pending queue, and let it start over from scratch.
,
Jul 25 2016
Ok, I've done that, and the bot is up and waiting for its next build request. The most recent green builds were all taking about the same amount of time (40-50m) as the green builds before the swaths of exceptions and failures. So I'm hopeful that it will remain on top of its queue this time.
,
Jul 25 2016
It ran and completed in 43 minutes, although it did fail two tests (not surprising given that it basically just ran two or more days worth of changes). Leaving those failures to the sheriffs.
,
Jul 25 2016
FYI, I followed up on the failing tests. (Discovered bad change, reverted it.) |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by smut@chromium.org
, Jul 20 2016Labels: OS-Linux