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

Issue 913073 link

Starred by 1 user
Status: Untriaged
Owner:
█ djmm@chromium.org
Last visit > 30 days ago
Cc:
sdantul...@chromium.org
█ kbleicher@chromium.org
mkarkada@chromium.org
█ djmm@chromium.org
dchan@chromium.org
abod...@chromium.org
█ bhthompson@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

scarlet-arcnext stuck on R70 dev because AU is failing

Project Member Reported by dhadd...@chromium.org, Dec 7 
Most boards on are on R72 dev:
https://cros-goldeneye.corp.google.com/chromeos/console/listOmaha

scarlet-arcnext/scarlet is still on R70 because every AU test fails updating from 11005.1.0:
https://stainless.corp.google.com/search?view=matrix&row=board_model&col=build&first_date=2018-12-03&last_date=2018-12-07&suite=%5Epaygen_au_dev&board=scarlet-arcnex&model=scarlet&exclude_cts=false&exclude_not_run=false&exclude_non_release=true&exclude_au=false&exclude_acts=true&exclude_retried=true&exclude_non_production=false

The failure reason is:
"Build dev-channel/scarlet-arcnext/11005.1.0 failed to boot on chromeos6-row2-rack6-host12; system rolled back to previous build"

+Tpms to see if this is something they care about

Comment 1 by dhadd...@chromium.org, Dec 11

Owner: djmm@chromium.org

Comment 2 by kbleicher@google.com, Dec 11

Cc: bhthompson@chromium.org dchan@chromium.org
Labels: M-72

Comment 3 by bhthompson@google.com, Dec 11 

I don't think scarlet-arcnext is being used so much in a dogfood context, this is an internal only build for engineering, so priority is not super high.

If the old build 11005.1 is failing, how do we stop bothering trying to boot that version? Do we need to just force a new dev push out so the AU tests get unwedged?

Comment 4 by dhaddock@google.com, Dec 11 

Yeah that would do it
►

Sign in to add a comment