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
Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment
coral release hasn't passed since build 599
Project Member Reported by martinroth@chromium.org, Dec 20 Back to list
Every coral release build since build 599 has failed.  This build is building for astronaut, nasher, nasher360, robo, robo360, and santa.  The platforms are failing for different reasons.

In build 618, we had one ssh failure on robo360, and this killed all the other tests.
 
Cc: renyi@chromium.org semenzato@chromium.org
Labels: Hotlist-CrOS-Sheriffing
Owner: semenzato@chromium.org
Status: Assigned
Sheriffs, PTAL
Cc: bhthompson@chromium.org
Labels: -Pri-3 OS-Chrome Pri-2
I have noticed the coral failures and I suspect issue 788584, which is currently assigned to an engineer who is OOO and will be back on Jan 8.  I asked (on the bug) if someone else can take a look.  I can escalate.

I am not sure where the failures for the other platforms can be seen.  Can someone comment?

I don't think this is an infrastructure bug, but we'll leave this in that category for now.
Also note issue 783832 for the cheets_StartAndroid.stress test failures.  I am not sure if it is related to issue 788584.

This bug is too generic and is not adding any information.  As long as you're looking at logs, please open a bug for each separate failure?

Just a friendly nudge, the coral-release is still failing. Only one success at build 678. It looks like it has a ton of different failures.
Sign in to add a comment