nyan-chrome-pfq failed to build during install phase |
|||||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/nyan-chrome-pfq/builds/2929 Looks like the build failed during install phase for some rsync error. factory-0.2.0-r377: Creating factory bundle in /build/nyan/tmp/portage/chromeos-base/factory-0.2.0-r377/image/usr/local/factory/bundle... factory-0.2.0-r377: symlink has no referent: "/build/nyan/tmp/portage/chromeos-base/factory-0.2.0-r377/work/factory-0.2.0/setup/netboot_firmware_settings.py" factory-0.2.0-r377: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2] factory-0.2.0-r377: tput: unknown terminal "unknown" factory-0.2.0-r377: tput: unknown terminal "unknown" factory-0.2.0-r377: tput: unknown terminal "unknown" factory-0.2.0-r377: ERROR: Unexpected failure (exit code: 23). Abort. factory-0.2.0-r377: make: *** [Makefile:309: bundle] Error 23 factory-0.2.0-r377: * ERROR: chromeos-base/factory-0.2.0-r377::chromiumos failed (install phase): factory-0.2.0-r377: * emake failed
,
Jun 30 2017
The error message suggests a broken symlink I see that nyan-chrome-pfq hasn't been running the past few days; is that intended?
,
Jun 30 2017
I notice that too. It has not been run since 6/28. Does anyone disable it?
,
Jun 30 2017
I saw something about replacing nyan with nyan_big? +bhthompson@
,
Jun 30 2017
It is swapped out, the new nyan_big version should instantiate on the next waterfall restart. I don't think the lack of nyan should cause it to fail the pfq overall though, if it does we should file a bug to ensure that only instantiated important builds can block the master.
,
Jun 30 2017
Swap out CL: https://chromium-review.googlesource.com/c/548437/ chromite pin has been updated: https://chrome-internal-review.googlesource.com/c/405169/ This is pending a chromeos waterfall restart. +akeshet next week's deputy
,
Jun 30 2017
Update from offline discussion at crosoncall.
Executive summary:
* The fix requires a waterfall restart. That should be all
that's needed.
* Waterfall restarts are a bad idea late Friday before a four-day
holiday.
* Although this problem is holding up the Chrome PFQ, it's not
the only thing holding up the PFQ.
So, we don't have a problem urgent enough to require the risk of
a waterfall restart right now. That will need to arrange to happen
7/5.
Copying next week's deputies, since they're likely to be involved.
,
Jun 30 2017
> * The fix requires a waterfall restart. That should be all > that's needed. Also, looking at this bug, I think someone should test the assertion above more carefully. I can't explain why the nyan builder would have broken because there's a pending swap to "nyan_big".
,
Jun 30 2017
Following up on c#8, I note also that there's no nyan_release builder. So "nyan" could be broken, and only the PFQ might notice.
,
Jun 30 2017
Re comment 9, this is why I wanted to swap it out, I don't trust vanilla nyan to stay reliable since we only test its variants.
,
Jun 30 2017
FWIW, I build with BOARD=nyan in a local chroot from ToT, and it worked fine. I'm not sure how much that proves, but I think it ain't chopped liver... At any rate, the long term fix is to restart the waterfall.
,
Jul 5 2017
+current gardeners
,
Jul 17 2017
ChromeOS Infra P1 Bugscrub. P1 Bugs in this component should be important enough to get weekly status updates. Is this already fixed? -> Fixed Is this no longer relevant? -> Archived or WontFix Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority. Is this a Feature Request rather than a bug? Type -> Feature Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign. Does this bug have the wrong owner? -> reassign. Bugs that remain in this state next week will be downgraded to P2.
,
Jul 24 2017
Can't replicate as nyan-chrome-pfq is no longer a builder (https://uberchromegw.corp.google.com/i/chromeos/builders/nyan-chrome-pfq) |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by jen...@chromium.org
, Jun 30 2017