On Sun, Jun 21, 2020 at 5:00 PM Richard Purdie <richard.pur...@linuxfoundation.org> wrote: > > On Sun, 2020-06-21 at 16:24 +0100, Alex Kiernan wrote: > > Hi Richard > > > > On Sat, Jun 20, 2020 at 1:45 PM Richard Purdie > > <richard.pur...@linuxfoundation.org> wrote: > > > On Tue, 2020-06-09 at 16:08 +0100, Alex Kiernan wrote: > > > > On Thu, May 21, 2020 at 3:14 PM Alex Kiernan via > > > > lists.openembedded.org < > > > > alex.kiernan=gmail....@lists.openembedded.org > > > > wrote: > > > > > Hi Ross > > > > > > > > > > On Thu, Jan 2, 2020 at 11:20 PM Ross Burton < > > > > > ross.bur...@intel.com> > > > > > wrote: > > > > > > On 19/12/2019 22:17, Alex Kiernan wrote: > > > > > > > Enable rootfs_check_host_user_contaminated by default > > > > > > > > > > > > Useful check! > > > > > > > > > > > > WARNING: Paths in the rootfs are owned by the same user or > > > > > > group > > > > > > as the > > > > > > user running bitbake. See the logfile for the specific paths. > > > > > > > > > > > > /data/poky-tmp/master/work/intel_corei7_64-poky-linux/core- > > > > > > image- > > > > > > sato/1.0-r0/rootfs/usr/share/fonts/.uuid > > > > > > > > > > > > /data/poky-tmp/master/work/intel_corei7_64-poky-linux/core- > > > > > > image- > > > > > > sato/1.0-r0/rootfs/usr/share/fonts/ttf/.uuid > > > > > > > > > > > > (patch incoming) > > > > > > > > > > > > > > > > Did you manage to get a patch for this out? I've had a couple > > > > > of > > > > > goes > > > > > at reproducing it and failed, but I suspect I'm not including > > > > > the > > > > > right things. It would be good to get this check enabled early > > > > > in > > > > > the > > > > > release cycle, if we can? > > > > > > > > > > > > > Ping? > > > > > > I'm trying to enable this but its triggering warnings on the > > > autobuilder: > > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/2037 > > > > > > Unfortunately the logs are totally useless. I think we'll have to > > > improve the logging before this can be debugged and fixed which > > > blocks > > > this merging. > > > > > > > I've had a couple of goes at reproducing this locally, based on the > > configuration I think it's building and can't get it to fail... > > > > Presumably we need to expose the failure lines from the supplementary > > log file so that they make it into the autobuilder output? > > Yes, we need the output to show which files are affected to have some > chance of figuring out how to fix this. The fact its happening > intermittently is somewhat worrying :/. >
Just sent a v2 which includes changes to push the failure paths into the main log > Cheers, > > Richard > -- Alex Kiernan
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#139731): https://lists.openembedded.org/g/openembedded-core/message/139731 Mute This Topic: https://lists.openembedded.org/mt/72390300/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
