On Mon, 2020-06-22 at 19:53 +0100, Alex Kiernan wrote: > On Mon, Jun 22, 2020 at 6:34 PM Richard Purdie > <[email protected]> wrote: > > On Mon, 2020-06-22 at 11:57 +0100, Alex Kiernan wrote: > > > Generate output for each contaminated path so it's visible in the main > > > log file, then enable rootfs_check_host_user_contaminated by default. > > > > > > Signed-off-by: Alex Kiernan <[email protected]> > > > --- > > > > > > Changes in v2: > > > - expose each contaminated path in the main log > > > > > > meta/classes/rootfs-postcommands.bbclass | 9 ++++----- > > > 1 file changed, 4 insertions(+), 5 deletions(-) > > > > Thanks, this is definitely more helpful. Some warnings in the test > > build: > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/2046 > > > > step1b: WARNING: core-image-sato-sdk-1.0-r0 do_rootfs: Path in the rootfs > > is owned by the same user or group as the user running bitbake: > > /var/lib/nfs/statd > > step1b: WARNING: core-image-sato-sdk-1.0-r0 do_rootfs: Path in the rootfs > > is owned by the same user or group as the user running bitbake: > > /var/lib/nfs/statd/sm.bak > > step1b: WARNING: core-image-sato-sdk-1.0-r0 do_rootfs: Path in the rootfs > > is owned by the same user or group as the user running bitbake: > > /var/lib/nfs/statd/state > > step1b: WARNING: core-image-sato-sdk-1.0-r0 do_rootfs: Path in the rootfs > > is owned by the same user or group as the user running bitbake: > > /var/lib/nfs/statd/sm > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/2073 > > > > step3b: WARNING: core-image-sato-1.0-r0 do_rootfs: Path in the rootfs is > > owned by the same user or group as the user running bitbake: > > /var/cache/fontconfig/CACHEDIR.TAG > > > > which does raise more questions. > > > > I'm having no luck reproducing either of these locally :|
They don't reproduce on the autobuilder either. We're probably going to need to open a bug in bugzilla and enter these there listing the target that caused it and the host it was on. Hopefully we'll see a pattern emerge. Or maybe the pseudo fix I posted will make it all go away. I can live in hope right?! Either way, I think this patch is going to be a longer journey until we figure out what is happening. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#139791): https://lists.openembedded.org/g/openembedded-core/message/139791 Mute This Topic: https://lists.openembedded.org/mt/75035700/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
