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

Issue 741951 link

Starred by 2 users
Status: Archived
Owner:
█ jrbarnette@chromium.org
Last visit > 30 days ago
Closed: Jul 2017
Cc:
akes...@chromium.org
derat@chromium.org
dgarr...@chromium.org
vapier@chromium.org
d...@chromium.org
█ rcui@chromium.org
█ jrbarnette@chromium.org
glevin@chromium.org
dpranke@chromium.org
steve...@chromium.org
achuith@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug

Blocked on:
issue 744752


Sign in to add a comment

daisy-full prebuilts not updated since 6/28/17

Project Member Reported by steve...@chromium.org, Jul 13 2017 
The latest LATEST file for daisy-full (which is what is used in Simple Chrome with --use-external-config for the chromium waterfall) is   LATEST-9692.0.0:

https://pantheon.corp.google.com/storage/browser/chromeos-image-archive/daisy-full/?prefix=LATEST-969

The timing suggests this may be related to  issue 741765  ?

I'm not actually sure where / how the -full LATEST- files get updated.

This is preventing us from uprevving the Simple Chrome CrOS SDK version (i.e. it is potentially causing https://chromium-review.googlesource.com/c/568527/ to fail, although there appears to be another issue causing a different failure, but it might just be a different symptom for the same problem)

Marking as a P0 because Simple Chrome is currently using CrOS 9588.0.0 which is several weeks old. (The latest successful PFQ run is 9733.0.0)

Comment 1 by steve...@chromium.org, Jul 13 2017 

I just realized that the amd64-generic-full prebuilds are being updated so this is probably unrelated to  issue 741765 .

Did we maybe remove daisy chromiumos coverage from the waterfall?

(I have no idea why we use daisy instead of arm-generic BTW)

Comment 2 by steve...@chromium.org, Jul 13 2017 

We do have arm-generic prebuilts, maybe we should just update the chromium waterfall (and chromiumos.chromium waterfall) to use arm-generic? That would be *so* much less confusing than using a board that is probably rapidly approaching its EOL...

Comment 3 by steve...@chromium.org, Jul 13 2017

Cc: vapier@chromium.org
+vapier@

Comment 4 by vapier@chromium.org, Jul 13 2017 

looks like the public waterfall isn't scheduling daisy-full:
https://uberchromegw.corp.google.com/i/chromiumos/builders/daisy-full
  offline
  1449 pending

Comment 5 by steve...@chromium.org, Jul 17 2017 

We need a solution for this asap, any thoughts here?

Comment 6 by steve...@chromium.org, Jul 17 2017

Owner: jrbarnette@chromium.org
Status: Assigned (was: Untriaged)
-> jrbarnette@ to investigate why daisy-full is not updating.

We seem to have a lot of active daisy builders, so I think we should revisit the daisy vs arm-generic discussion another day.

Comment 7 by vapier@chromium.org, Jul 17 2017 

yeah, let's not turn this into a daisy-vs-arm discussion.  the daisy-full builder is on the public waterfall but not being scheduled (anymore).  that needs fixing.  the last run corresponds with the dates here as to when things stopped working.

Comment 8 by achuith@chromium.org, Jul 17 2017

Blockedon: 744752

Comment 9 by dgarr...@chromium.org, Jul 17 2017 

This should also be fixed, now that Richard fixed the builder by restarting it.

Comment 10 by dgarr...@chromium.org, Jul 17 2017

Status: Fixed (was: Assigned)

Comment 11 by steve...@chromium.org, Jul 18 2017

Cc: dpranke@chromium.org d...@chromium.org steve...@chromium.org
 Issue 741937  has been merged into this issue.

Comment 12 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)
►

Sign in to add a comment