snappy-release: BuildImage phase failed at build_packages |
||||
Issue descriptionBuilder: snappy-release Build: https://chromegw.corp.google.com/i/chromeos/builders/snappy-release/builds/717 Logs: Failed chromeos-base/chromeos-init-0.0.25-r2922 (in 0m2.3s). Your build has failed. Pending 9/393, [Time 12:50:59 | Elapsed 1m38.5s | Load 17.38 10.37 15.07] Packages failed: chromeos-base/chromeos-init-0.0.25-r2922
,
Jun 9 2017
I'm working on Reef/Snappy. I'll take a look.
,
Jun 9 2017
My local build of snappy did not have this problem. I kicked a trybot to see if it reproduces there. https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/release/builds/11963
,
Jun 9 2017
Oops, I got the wrong trybot. Here it is: https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/release/builds/11964 Failed the same way. Looks like rootfs is too big for snappy. :(.
,
Jun 12 2017
,
Jun 12 2017
This CL may have exceeded the size of the rootfs allocation: https://chrome-internal.googlesource.com/chromeos/chromeos-assets/+/466a38834b9bb227df53075a5e5cc799b40bd21f A new help app was just landed.
,
Jun 22 2017
Looks like this was fixed on June 13. Snappy builds don't fail build image after build 731. https://uberchromegw.corp.google.com/i/chromeos/builders/snappy-release?numbuilds=50 |
||||
►
Sign in to add a comment |
||||
Comment 1 by dgarr...@chromium.org
, Jun 9 2017