Corrupt chroot causes uprevved emerge failure? |
||||
Issue descriptionThis build run failed on 56 slaves. https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/16563 Building chromite failed with this error: chromite-0.0.2-r3429: * forbidden by PMS section 13.4 (see bug #326685): chromite-0.0.2-r3429: * chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/swarming.client/.git/objects chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/swarming.client/.git/hooks chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/swarming.client/.git/rr-cache chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/swarming.client/.git/logs chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/swarming.client/.git/svn chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/swarming.client/.git/info chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/swarming.client/.git/refs chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/pyelftools/.git/objects chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/pyelftools/.git/hooks chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/pyelftools/.git/rr-cache chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/pyelftools/.git/logs chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/pyelftools/.git/svn chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/pyelftools/.git/info chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/pyelftools/.git/refs chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/dpkt/.git/objects chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/dpkt/.git/hooks chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/dpkt/.git/rr-cache chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/dpkt/.git/logs chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/dpkt/.git/svn chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/dpkt/.git/info chromite-0.0.2-r3429: * /build/nyan_kitty/usr/lib/python2.7/site-packages/chromite/third_party/dpkt/.git/refs The two chromite CLs in the CQ looked innocent, and passed on the following CQ run. Every builder I checked was reusing a chroot from the previous run. Every builder I checked created a new chroot on the following CQ run. I don't understand what happened, but believe it to either be a bad chroot state left from the previous run, or an recurring issue that was covered up by the recreation of the chroots.
,
Oct 13 2017
probably related to the portage CL: https://chromium-review.googlesource.com/559225
,
Oct 13 2017
Reasonable, except it wasn't in the failed build, or the build before it. https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/16552 https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/16563
,
Oct 13 2017
bmgordon@ I believe that when your project is stable, we can afford to more aggressively roll back the chroot to a known good state and avoid this kind of failure.
,
May 11 2018
,
May 11 2018
If this was caused by bad chroot reuse, it should be fixed by the recently landed parts of crbug.com/829665 . Even if that wasn't the cause, we haven't seen any further occurrences, so I don't think there's anything more to do here. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dgarr...@chromium.org
, Oct 13 2017