[OE-core] [PATCH 1/3] dbus-test: Fix QA host-contamination errors

[Richard Purdie]

On Sun, 2020-03-01 at 08:20 +0000, Richard Purdie wrote:
> On Sun, 2020-03-01 at 00:17 -0800, Khem Raj wrote:
> > 
> > On Sun, Mar 1, 2020 at 12:14 AM Richard Purdie <
> > richard.purdie at linuxfoundation.org> wrote:
> > > On Sun, 2020-03-01 at 00:12 -0800, Khem Raj wrote:
> > > > 
> > > > On Sat, Feb 29, 2020 at 11:57 PM Richard Purdie <
> > > > Why aren't we seeing this everywhere? The autobuilders don't
> > > show
> > > > > it
> > > > > and no other reports. What is unique to your setup to
> > > > > reproduce
> > > > > this?
> > > > 
> > > > These are QA warnings by default and in my distro I turned it
> > > into
> > > > error so they were being reported before too 
> > > 
> > > The autobuilder would show any warnings or errors and we're not
> > > seeing
> > > either.
> > > 
> > > > Secondly this is a Debian10 minimum container running in docker
> > > where
> > > > the user id is 1000 for the build user other than that there is
> > > > nothing special 
> > > 
> > > We run debian10 builders on the autobuilder.
> > > 
> > > I just don't understand why weren't not seeing this everywhere.
> > > We
> > > really need to understand why this is :/.
> > 
> > From what you see from fixes what it’s reporting are legit errors 
> > Why it’s not showing up everywhere I am not sure
> > I don’t see it on Ubuntu 18.04 boxes without docker as well 
> 
> I understand the need for the fixes, I'm just very concerned we have
> what amounts to undetected non-determinism in the build :(
> 
> I'm more concerned about fixing that (and ensuring we can detect/fix
> all cases) than I am about the individual errors.

I did a bit more thinking/checking on this.

An interesting command to experiment with is:

$ touch /tmp/test; ls -la /tmp/test; ./tmp/sysroots-components/x86_64/pseudo-native/usr/bin/pseudo sh -c "ls -la /tmp/test*; cp /tmp/test /tmp/test2; ls -la /tmp/test*; rm /tmp/test*"

which for me shows:

-rw-rw-r-- 1 richard richard 0 Mar  1 17:03 /tmp/test
Warning: PSEUDO_PREFIX unset, defaulting to XXX./tmp/sysroots-components/x86_64/pseudo-native/usr.
-rw-rw-r-- 1 1000 1000 0 Mar  1 17:03 /tmp/test
-rw-rw-r-- 1 1000 1000 0 Mar  1 17:03 /tmp/test
-rw-rw-r-- 1    0    0 0 Mar  1 17:03 /tmp/test2

Can you see if that is different on your two machines?

If so, lets have a look at the output of:

touch /tmp/test; ls -la /tmp/test; PSEUDO_DEBUG=nfoPdeViDxy ./tmp/sysroots-components/x86_64/pseudo-native/usr/bin/pseudo sh -c "ls -la /tmp/test*; cp /tmp/test /tmp/test2; ls -la /tmp/test*; rm /tmp/test*"

which turns on pseudo's debug output and see if that sheds some light
on why this is behaving differently, perhaps because its under docker?

Cheers,

Richard