New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

rmi4update kills chrome on nautilus

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Apr 13

Issue description

Cc: pbe...@chromium.org jrbarnette@chromium.org
Owner: cmtm@chromium.org
separate this one out from b/832530
Labels: Hotlist-CrOS-Sheriffing
Owner: jkop@chromium.org
Summary: chromeos2-row8-rack9-host3: AU fails on this particular unit repeatedly (was: nautilus-release:532 failed)
provision     FAIL: Unhandled DevServerException: CrOS auto-update failed for host chromeos2-row8-rack9-host3: 0) RootfsUpdateError: After update and reboot, Chrome failed to reach login screen within 180 seconds, 1)  Timeout occurred- waited 1800.0 seconds.. The CrOS auto-update pro...

Looking back several builds, it's always the same unit creating problems.
Status: Assigned (was: Available)
Owner: pbe...@chromium.org
> Looking back several builds, it's always the same unit creating problems.

That DUT is only the unluckiest victim.  Three DUTs have seen the failure
in the past 24 hours:
    $ dut-status -b nautilus -p bvt -f | grep provision | grep -v OK
        2018-04-13 14:47:30  -- http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row8-rack9-host3/63009617-provision/
        2018-04-13 07:53:23  -- http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row8-rack9-host3/63007598-provision/
        2018-04-13 06:44:15  -- http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row8-rack9-host3/63007142-provision/
        2018-04-12 20:37:05  -- http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row8-rack9-host5/63003818-provision/
        2018-04-12 19:26:36  -- http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row8-rack9-host5/63003449-provision/
        2018-04-12 19:07:58  -- http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row8-rack9-host8/63003343-provision/

Regarding this:
    After update and reboot, Chrome failed to reach login screen within 180 seconds

That error usually indicates a Chrome crash (or hang) at boot time.  Looking
in the logs for the provision failures, I don't see any Chrome crashes.
However, I do see crashes like this:
    rmi4update.20180413.215245.1602.core

I've no idea what that is, but it's instantly the prime suspect.


Summary: Chrome crash on nautilus (was: chromeos2-row8-rack9-host3: AU fails on this particular unit repeatedly)
The first instance of the failure is here:
    https://luci-milo.appspot.com/buildbot/chromeos/nautilus-release/525

That's the canary at 3:00AM on 4/11.

This problem hasn't happened on every build since, but it's been pretty
common, so most likely, that's the build with the blamelist to chase.

Summary: rmi4update kills chrome on nautilus (was: Chrome crash on nautilus)
Let's call it like it is.

Build #525 had Chrome 67.0.3390.0.  So did a half-dozen or more builds
before it.  So, this wasn't caused by a Chrome change; it has to be an
OS change, and the rmi4update crashes can't be coincidence.

Sign in to add a comment