[PATCH 0/3] Fix host contamination QA errors

[PATCH 0/3] Fix host contamination QA errors

[Khem Raj]

These patches fix host-user-contaminated QA issues

Khem Raj (3):
  dbus-test: Fix QA host-contamination errors
  strace: Fix host contamination QA errors
  boost: Fix host-user-contaminated QA errors

 meta/recipes-core/dbus/dbus-test_1.12.16.bb   |  4 +--
 .../strace/0001-Evaluate-AC_PROG_LN_S.patch   | 29 +++++++++++++++++++
 meta/recipes-devtools/strace/strace_5.5.bb    |  1 +
 meta/recipes-support/boost/boost.inc          |  1 +
 4 files changed, 33 insertions(+), 2 deletions(-)
 create mode 100644 meta/recipes-devtools/strace/strace/0001-Evaluate-AC_PROG_LN_S.patch

-- 
2.25.1

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

[Khem Raj]

Errors like below are fixed

bus/connection.h is owned by uid 1000, which is the same as t
he user running bitbake. This may be due to host contamination

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 meta/recipes-core/dbus/dbus-test_1.12.16.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-core/dbus/dbus-test_1.12.16.bb b/meta/recipes-core/dbus/dbus-test_1.12.16.bb
index bea0e74ed0..91e2ba69d2 100644
--- a/meta/recipes-core/dbus/dbus-test_1.12.16.bb
+++ b/meta/recipes-core/dbus/dbus-test_1.12.16.bb
@@ -70,11 +70,11 @@ do_install_ptest() {
 
 	install ${B}/test/test-segfault ${D}${PTEST_PATH}/test
 
-	cp -r ${B}/test/data ${D}${PTEST_PATH}/test
+	cp -R --no-dereference --preserve=mode,links ${B}/test/data ${D}${PTEST_PATH}/test
 	install ${B}/dbus/.libs/test-dbus ${D}${PTEST_PATH}/test
 
 	install -d ${D}${PTEST_PATH}/test/.libs
-	cp -a ${B}/dbus/.libs/*.so* ${D}${PTEST_PATH}/test/.libs
+	cp -R --no-dereference --preserve=mode,links ${B}/dbus/.libs/*.so* ${D}${PTEST_PATH}/test/.libs
 
 	# Remove build host references...
 	find "${D}${PTEST_PATH}/test/data" \( -name *.service -o -name *.conf -o -name "*.aaprofile" \) -type f -exec \
-- 
2.25.1

[PATCH 2/3] strace: Fix host contamination QA errors

[Khem Raj]

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 .../strace/0001-Evaluate-AC_PROG_LN_S.patch   | 29 +++++++++++++++++++
 meta/recipes-devtools/strace/strace_5.5.bb    |  1 +
 2 files changed, 30 insertions(+)
 create mode 100644 meta/recipes-devtools/strace/strace/0001-Evaluate-AC_PROG_LN_S.patch

diff --git a/meta/recipes-devtools/strace/strace/0001-Evaluate-AC_PROG_LN_S.patch b/meta/recipes-devtools/strace/strace/0001-Evaluate-AC_PROG_LN_S.patch
new file mode 100644
index 0000000000..c956256bed
--- /dev/null
+++ b/meta/recipes-devtools/strace/strace/0001-Evaluate-AC_PROG_LN_S.patch
@@ -0,0 +1,29 @@
+From 49e58e2d8ada869ebc75ab6e17c80e20e00ee625 Mon Sep 17 00:00:00 2001
+From: Khem Raj <raj.khem@gmail.com>
+Date: Sat, 29 Feb 2020 13:21:08 -0800
+Subject: [PATCH] Evaluate AC_PROG_LN_S
+
+Fixes
+strace: /usr/lib/strace/ptest/tests/ioctl_evdev-success-Xverbose.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
+
+Upstream-Status: Pending
+Signed-off-by: Khem Raj <raj.khem@gmail.com>
+---
+ configure.ac | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/configure.ac b/configure.ac
+index 65f000b..c4cbf55 100644
+--- a/configure.ac
++++ b/configure.ac
+@@ -25,6 +25,7 @@ AC_CONFIG_HEADERS([config.h])
+ AM_INIT_AUTOMAKE([foreign nostdinc dist-xz silent-rules parallel-tests subdir-objects 1.13])
+ AM_MAINTAINER_MODE
+ AC_CANONICAL_HOST
++AC_PROG_LN_S
+ 
+ RPM_CHANGELOGTIME="$(LC_TIME=C date -u '+%a %b %d %Y')"
+ AC_SUBST(RPM_CHANGELOGTIME)
+-- 
+2.25.1
+
diff --git a/meta/recipes-devtools/strace/strace_5.5.bb b/meta/recipes-devtools/strace/strace_5.5.bb
index 6e7d63949d..f3b7c4462e 100644
--- a/meta/recipes-devtools/strace/strace_5.5.bb
+++ b/meta/recipes-devtools/strace/strace_5.5.bb
@@ -13,6 +13,7 @@ SRC_URI = "https://strace.io/files/${PV}/strace-${PV}.tar.xz \
            file://0001-caps-abbrev.awk-fix-gawk-s-path.patch \
            file://ptest-spacesave.patch \
            file://uintptr_t.patch \
+           file://0001-Evaluate-AC_PROG_LN_S.patch \
            "
 SRC_URI[md5sum] = "dbce2e84632b39a4ed86b9fc60447af9"
 SRC_URI[sha256sum] = "9f58958c8e59ea62293d907d10572e352b582bd7948ed21aa28ebb47e5bf30ff"
-- 
2.25.1

[PATCH 3/3] boost: Fix host-user-contaminated QA errors

[Khem Raj]

bjam calls cp directly, which can install with same user name as bitbake
in staging, which is caught by packager and reported, therefore override
cp command to use right options to make cp behave like install utility

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 meta/recipes-support/boost/boost.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc
index e15dce4e1d..7f44638135 100644
--- a/meta/recipes-support/boost/boost.inc
+++ b/meta/recipes-support/boost/boost.inc
@@ -189,6 +189,7 @@ do_compile() {
 }
 
 do_install() {
+        export CP="cp -R --no-dereference --preserve=mode,links"
 	bjam ${BJAM_OPTS} \
 		--libdir=${D}${libdir} \
 		--includedir=${D}${includedir} \
-- 
2.25.1

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

[Richard Purdie]

On Sat, 2020-02-29 at 17:42 -0800, Khem Raj wrote:
> Errors like below are fixed
> 
> bus/connection.h is owned by uid 1000, which is the same as t
> he user running bitbake. This may be due to host contamination
> 
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
>  meta/recipes-core/dbus/dbus-test_1.12.16.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

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?

Cheers,

Richard

> diff --git a/meta/recipes-core/dbus/dbus-test_1.12.16.bb
> b/meta/recipes-core/dbus/dbus-test_1.12.16.bb
> index bea0e74ed0..91e2ba69d2 100644
> --- a/meta/recipes-core/dbus/dbus-test_1.12.16.bb
> +++ b/meta/recipes-core/dbus/dbus-test_1.12.16.bb
> @@ -70,11 +70,11 @@ do_install_ptest() {
>  
>  	install ${B}/test/test-segfault ${D}${PTEST_PATH}/test
>  
> -	cp -r ${B}/test/data ${D}${PTEST_PATH}/test
> +	cp -R --no-dereference --preserve=mode,links ${B}/test/data
> ${D}${PTEST_PATH}/test
>  	install ${B}/dbus/.libs/test-dbus ${D}${PTEST_PATH}/test
>  
>  	install -d ${D}${PTEST_PATH}/test/.libs
> -	cp -a ${B}/dbus/.libs/*.so* ${D}${PTEST_PATH}/test/.libs
> +	cp -R --no-dereference --preserve=mode,links
> ${B}/dbus/.libs/*.so* ${D}${PTEST_PATH}/test/.libs
>  
>  	# Remove build host references...
>  	find "${D}${PTEST_PATH}/test/data" \( -name *.service -o -name
> *.conf -o -name "*.aaprofile" \) -type f -exec \
> -- 
> 2.25.1
> 

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

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 2010 bytes --]

On Sat, Feb 29, 2020 at 11:57 PM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Sat, 2020-02-29 at 17:42 -0800, Khem Raj wrote:
> > Errors like below are fixed
> >
> > bus/connection.h is owned by uid 1000, which is the same as t
> > he user running bitbake. This may be due to host contamination
> >
> > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > ---
> >  meta/recipes-core/dbus/dbus-test_1.12.16.bb | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
>
> 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

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

>
>
> Cheers,
>
> Richard
>
> > diff --git a/meta/recipes-core/dbus/dbus-test_1.12.16.bb
> > b/meta/recipes-core/dbus/dbus-test_1.12.16.bb
> > index bea0e74ed0..91e2ba69d2 100644
> > --- a/meta/recipes-core/dbus/dbus-test_1.12.16.bb
> > +++ b/meta/recipes-core/dbus/dbus-test_1.12.16.bb
> > @@ -70,11 +70,11 @@ do_install_ptest() {
> >
> >       install ${B}/test/test-segfault ${D}${PTEST_PATH}/test
> >
> > -     cp -r ${B}/test/data ${D}${PTEST_PATH}/test
> > +     cp -R --no-dereference --preserve=mode,links ${B}/test/data
> > ${D}${PTEST_PATH}/test
> >       install ${B}/dbus/.libs/test-dbus ${D}${PTEST_PATH}/test
> >
> >       install -d ${D}${PTEST_PATH}/test/.libs
> > -     cp -a ${B}/dbus/.libs/*.so* ${D}${PTEST_PATH}/test/.libs
> > +     cp -R --no-dereference --preserve=mode,links
> > ${B}/dbus/.libs/*.so* ${D}${PTEST_PATH}/test/.libs
> >
> >       # Remove build host references...
> >       find "${D}${PTEST_PATH}/test/data" \( -name *.service -o -name
> > *.conf -o -name "*.aaprofile" \) -type f -exec \
> > --
> > 2.25.1
> >
>
>

[-- Attachment #2: Type: text/html, Size: 3193 bytes --]

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

[Richard Purdie]

On Sun, 2020-03-01 at 00:12 -0800, Khem Raj wrote:
> 
> 
> On Sat, Feb 29, 2020 at 11:57 PM Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
> > On Sat, 2020-02-29 at 17:42 -0800, Khem Raj wrote:
> > > Errors like below are fixed
> > > 
> > > bus/connection.h is owned by uid 1000, which is the same as t
> > > he user running bitbake. This may be due to host contamination
> > > 
> > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > > ---
> > >  meta/recipes-core/dbus/dbus-test_1.12.16.bb | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > 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 :/.

Cheers,

Richard

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

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 1659 bytes --]

On Sun, Mar 1, 2020 at 12:14 AM Richard Purdie <
richard.purdie@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 <
> > richard.purdie@linuxfoundation.org> wrote:
> > > On Sat, 2020-02-29 at 17:42 -0800, Khem Raj wrote:
> > > > Errors like below are fixed
> > > >
> > > > bus/connection.h is owned by uid 1000, which is the same as t
> > > > he user running bitbake. This may be due to host contamination
> > > >
> > > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > > > ---
> > > >  meta/recipes-core/dbus/dbus-test_1.12.16.bb | 4 ++--
> > > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > 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


>
> Cheers,
>
> Richard
>
>

[-- Attachment #2: Type: text/html, Size: 2636 bytes --]

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

[Richard Purdie]

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@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 <
> > > richard.purdie@linuxfoundation.org> wrote:
> > > > On Sat, 2020-02-29 at 17:42 -0800, Khem Raj wrote:
> > > > > Errors like below are fixed
> > > > > 
> > > > > bus/connection.h is owned by uid 1000, which is the same as t
> > > > > he user running bitbake. This may be due to host
> > contamination
> > > > > 
> > > > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > > > > ---
> > > > >  meta/recipes-core/dbus/dbus-test_1.12.16.bb | 4 ++--
> > > > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > > > 
> > > > 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.

Cheers,

Richard

Re: [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@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

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

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 3213 bytes --]



On 3/1/20 9:05 AM, Richard Purdie wrote:
> 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@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?

above cmd output is exactly same as yours.

-rw-r--r-- 1 build build 0 Mar  2 18:49 /tmp/test
Warning: PSEUDO_PREFIX unset, defaulting to 
/mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr.
-rw-r--r-- 1 1000 1000 0 Mar  2 18:49 /tmp/test
-rw-r--r-- 1 1000 1000 0 Mar  2 18:49 /tmp/test
-rw-r--r-- 1    0    0 0 Mar  2 18:49 /tmp/test2

> 
> 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?
> 

I have attached the logfile.

> Cheers,
> 
> Richard
> 
> 

[-- Attachment #2: pseudo.log --]
[-- Type: text/plain, Size: 38046 bytes --]

paes: append_element gave us '', current ''
paes: append_element gave us '/mnt', current ''
paes: append_element gave us '/mnt/b', current ''
paes: append_element gave us '/mnt/b/yoe', current ''
paes: append_element gave us '/mnt/b/yoe/build', current ''
paes: append_element gave us '/mnt/b/yoe/build/.', current ''
paes: append_element gave us '/mnt/b/yoe/build/./tmp', current ''
paes: append_element gave us '/mnt/b/yoe/build/./tmp/sysroots-components', current ''
paes: append_element gave us '/mnt/b/yoe/build/./tmp/sysroots-components/x86_64', current ''
paes: append_element gave us '/mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native', current ''
paes: append_element gave us '/mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr', current ''
paes: append_element gave us '/mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/bin', current ''
paes: append_element gave us '/mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/bin/pseudo', current ''
Warning: PSEUDO_PREFIX unset, defaulting to /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr.
pseudo_env: PSEUDO_PREFIX => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr
pseudo_env: PSEUDO_BINDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/bin
pseudo_env: PSEUDO_LIBDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/lib/pseudo/lib
pseudo_env: PSEUDO_LOCALSTATEDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/var/pseudo
pseudo_env: PSEUDO_OPTS => 
pseudo_env: PSEUDO_DEBUG => nfoPdDyeiVx
43: new pid: 43 [sh]
43: umask calling real syscall.
43: umask calling real syscall.
43: open calling real syscall.
43: fcntl calling real syscall.
43: close calling real syscall.
43: fcntl calling real syscall.
43: open calling real syscall.
43: fcntl calling real syscall.
43: close calling real syscall.
43: fcntl calling real syscall.
43: pathconf calling real syscall.
43: getcwd calling real syscall.
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/dev', current ''
43: paes: append_element gave us '/dev/tty', current ''
43: openat(path /dev/tty), flags 4002, stat rc 0, stat mode 20666
43: open /dev/tty [fd 3] (+buf) [dev/ino: 54/23598651] (020444): fcntl calling real syscall.
43: close calling real syscall.
43: fcntl calling real syscall.
43: open calling real syscall.
43: fchdir calling real syscall.
43: fchdir calling real syscall.
43: close calling real syscall.
43: msg type 1 (none), external path sh, mode 00
43: wrote 79 bytes
43: got header, type 4, pathlen 0
43: msg type 6 (open), external path /dev/tty, mode 020444
43: wrote 85 bytes
43: got header, type 4, pathlen 0
43: (43) succeed
43: close /dev/tty [fd 3]: (43) (no request)
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/mnt', current ''
43: paes: append_element gave us '/mnt/b', current ''
43: paes: append_element gave us '/mnt/b/yoe', current ''
43: paes: append_element gave us '/mnt/b/yoe/build', current ''
43: stat /mnt/b/yoe/build (+buf) (040755): msg type 3 (stat), external path /mnt/b/yoe/build, mode 040755
43: wrote 93 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 040755 uid 1000:100
43: paes: append_element gave us '/mnt/b/yoe/build', current ''
43: stat /mnt/b/yoe/build (+buf) (040755): msg type 3 (stat), external path /mnt/b/yoe/build, mode 040755
43: wrote 93 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 040755 uid 1000:100
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/mnt', current ''
43: stat /mnt (+buf) (040755): msg type 3 (stat), external path /mnt, mode 040755
43: wrote 81 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 040755 uid 0:0
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/mnt', current ''
43: paes: append_element gave us '/mnt/b', current ''
43: stat /mnt/b (+buf) (040755): msg type 3 (stat), external path /mnt/b, mode 040755
43: wrote 83 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 040755 uid 0:0
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/mnt', current ''
43: paes: append_element gave us '/mnt/b', current ''
43: paes: append_element gave us '/mnt/b/yoe', current ''
43: stat /mnt/b/yoe (+buf) (040755): msg type 3 (stat), external path /mnt/b/yoe, mode 040755
43: wrote 87 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 040755 uid 1000:100
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/mnt', current ''
43: paes: append_element gave us '/mnt/b', current ''
43: paes: append_element gave us '/mnt/b/yoe', current ''
43: paes: append_element gave us '/mnt/b/yoe/build', current ''
43: stat /mnt/b/yoe/build (+buf) (040755): msg type 3 (stat), external path /mnt/b/yoe/build, mode 040755
43: wrote 93 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 040755 uid 1000:100
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/mnt', current ''
43: paes: append_element gave us '/mnt/b', current ''
43: paes: append_element gave us '/mnt/b/yoe', current ''
43: stat /mnt/b/yoe (+buf) (040755): msg type 3 (stat), external path /mnt/b/yoe, mode 040755
43: wrote 87 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 040755 uid 1000:100
43: paes: append_element gave us '/mnt/b/yoe/build', current ''
43: stat /mnt/b/yoe/build (+buf) (040755): msg type 3 (stat), external path /mnt/b/yoe/build, mode 040755
43: wrote 93 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 040755 uid 1000:100
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/local', current ''
43: paes: append_element gave us '/usr/local/sbin', current ''
43: paes: append_element gave us '/usr/local/sbin/sh', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/local', current ''
43: paes: append_element gave us '/usr/local/bin', current ''
43: paes: append_element gave us '/usr/local/bin/sh', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/sbin', current ''
43: paes: append_element gave us '/usr/sbin/sh', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/bin', current ''
43: paes: append_element gave us '/usr/bin/sh', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/sbin', current ''
43: paes: append_element gave us '/sbin/sh', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: readlink calling real syscall.
43: paes: append_element gave us '/bin/bash', current ''
43: paes: append_element gave us '/bin/bash', current ''
43: stat /bin/bash (+buf) (0100755): msg type 3 (stat), external path /bin/bash, mode 0100755
43: wrote 86 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 0100755 uid 0:0
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: readlink calling real syscall.
43: paes: append_element gave us '/bin/bash', current ''
43: paes: append_element gave us '/bin/bash', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: readlink calling real syscall.
43: paes: append_element gave us '/bin/bash', current ''
43: paes: append_element gave us '/bin/bash', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: readlink calling real syscall.
43: paes: append_element gave us '/bin/bash', current ''
43: paes: append_element gave us '/bin/bash', current ''
43: stat /bin/bash (+buf) (0100755): msg type 3 (stat), external path /bin/bash, mode 0100755
43: wrote 86 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 0100755 uid 0:0
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: readlink calling real syscall.
43: paes: append_element gave us '/bin/bash', current ''
43: paes: append_element gave us '/bin/bash', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: readlink calling real syscall.
43: paes: append_element gave us '/bin/bash', current ''
43: paes: append_element gave us '/bin/bash', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/tmp', current ''
43: open /tmp [fd 3] (+buf) [dev/ino: 51/1685687] (041777): (43) (no request)
43: close /tmp [fd 3]: (43) (no request)
43: paes: append_element gave us '/mnt/b/yoe/build', current ''
43: stat /mnt/b/yoe/build (+buf) (040755): msg type 3 (stat), external path /mnt/b/yoe/build, mode 040755
43: wrote 93 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 040755 uid 1000:100
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/local', current ''
43: paes: append_element gave us '/usr/local/sbin', current ''
43: paes: append_element gave us '/usr/local/sbin/ls', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/local', current ''
43: paes: append_element gave us '/usr/local/bin', current ''
43: paes: append_element gave us '/usr/local/bin/ls', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/sbin', current ''
43: paes: append_element gave us '/usr/sbin/ls', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/bin', current ''
43: paes: append_element gave us '/usr/bin/ls', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/sbin', current ''
43: paes: append_element gave us '/sbin/ls', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/ls', current ''
43: stat /bin/ls (+buf) (0100755): msg type 3 (stat), external path /bin/ls, mode 0100755
43: wrote 84 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 0100755 uid 0:0
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/ls', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/ls', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/ls', current ''
43: stat /bin/ls (+buf) (0100755): msg type 3 (stat), external path /bin/ls, mode 0100755
43: wrote 84 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 0100755 uid 0:0
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/ls', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/ls', current ''
43: pseudo_env: PSEUDO_PREFIX => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr
43: pseudo_env: PSEUDO_BINDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/bin
43: pseudo_env: PSEUDO_LIBDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/lib/pseudo/lib
43: pseudo_env: PSEUDO_LOCALSTATEDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/var/pseudo
43: pseudo_env: PSEUDO_OPTS => 
43: pseudo_env: PSEUDO_DEBUG => nfoPdDyeiVx
43: pseudo_env: PSEUDO_DISABLED => 0
44: new pid: 44 [sh]
44: close calling real syscall.
44: getcwd calling real syscall.
44: paes: append_element gave us '', current ''
44: paes: append_element gave us '/bin', current ''
44: paes: append_element gave us '/bin/ls', current ''
44: exec /bin/ls: (44) (no request)
44: setting up envp environment.
44: new pid: 44 [ls]
44: umask calling real syscall.
44: umask calling real syscall.
44: open calling real syscall.
44: fcntl calling real syscall.
44: close calling real syscall.
44: fcntl calling real syscall.
44: open calling real syscall.
44: fcntl calling real syscall.
44: close calling real syscall.
44: fcntl calling real syscall.
44: pathconf calling real syscall.
44: getcwd calling real syscall.
44: paes: append_element gave us '', current ''
44: paes: append_element gave us '/proc', current ''
44: paes: append_element gave us '/proc/filesystems', current ''
44: fopen '/proc/filesystems': fd 3 <FILE 0x55b1f4c5b5f0>
44: open /proc/filesystems [fd 3] (+buf) [dev/ino: 53/4026532070] (0100444): fcntl calling real syscall.
44: close calling real syscall.
44: fcntl calling real syscall.
44: open calling real syscall.
44: fchdir calling real syscall.
44: fchdir calling real syscall.
44: close calling real syscall.
44: msg type 1 (none), external path ls, mode 00
44: wrote 79 bytes
44: got header, type 4, pathlen 0
44: msg type 6 (open), external path /proc/filesystems, mode 0100444
44: wrote 94 bytes
44: got header, type 4, pathlen 0
44: (44) succeed
44: close /proc/filesystems [fd 3]: (44) (no request)
44: paes: append_element gave us '', current ''
44: paes: append_element gave us '/etc', current ''
44: paes: append_element gave us '/etc/selinux', current ''
44: paes: append_element gave us '/etc/selinux/config', current ''
44: new pid: 44 [ls]
44: close calling real syscall.
44: getcwd calling real syscall.
44: paes: append_element gave us '', current ''
44: paes: append_element gave us '/tmp', current ''
44: paes: append_element gave us '/tmp/test', current ''
44: stat /tmp/test (+buf) (0100644): fcntl calling real syscall.
44: close calling real syscall.
44: fcntl calling real syscall.
44: open calling real syscall.
44: fchdir calling real syscall.
44: fchdir calling real syscall.
44: close calling real syscall.
44: msg type 1 (none), external path ls, mode 00
44: wrote 79 bytes
44: got header, type 4, pathlen 0
44: msg type 3 (stat), external path /tmp/test, mode 0100644
44: wrote 86 bytes
44: got header, type 4, pathlen 0
44: (44) fail mode 0100644 uid 1000:1000
44: paes: append_element gave us '', current ''
44: paes: append_element gave us '/tmp', current ''
44: paes: append_element gave us '/tmp/test', current ''
44: getxattr(/tmp/test [fd -1], security.selinux)
44: getxattr, name 'security.selinux'
44: combined path buffer at 0x55b1f4c5e460 [27 bytes]:
44: 0x000000 2f 74 6d 70  2f 74 65 73  74 00 73 65  63 75 72 69 '/tmp/test.securi'
44: 0x000010 74 79 2e 73  65 6c 69 6e  75 78 00                 'ty.selinux.'
44: get-xattr security.selinux -> /tmp/test (+buf) (0100644): msg type 3 (get-xattr), external path /tmp/test, mode 0100644
44: wrote 103 bytes
44: got header, type 4, pathlen 0
44: (44) fail
44: paes: append_element gave us '', current ''
44: paes: append_element gave us '/tmp', current ''
44: paes: append_element gave us '/tmp/test', current ''
44: getxattr(/tmp/test [fd -1], system.posix_acl_access)
44: getxattr, name 'system.posix_acl_access'
44: combined path buffer at 0x55b1f4c5e460 [34 bytes]:
44: 0x000000 2f 74 6d 70  2f 74 65 73  74 00 73 79  73 74 65 6d '/tmp/test.system'
44: 0x000010 2e 70 6f 73  69 78 5f 61  63 6c 5f 61  63 63 65 73 '.posix_acl_acces'
44: 0x000020 73 00                                              's.'
44: get-xattr system.posix_acl_access -> /tmp/test (+buf) (0100644): msg type 3 (get-xattr), external path /tmp/test, mode 0100644
44: wrote 110 bytes
44: got header, type 4, pathlen 0
44: (44) fail
-rw-r--r-- 1 1000 1000 0 Mar  2 18:46 /tmp/test
44: close  [fd 1]: (44) (no request)
44: close  [fd 2]: fcntl calling real syscall.
44: fcntl calling real syscall.
44: (44) (no request)
44: msg type 1 (none), external path ls, mode 00
44: wrote 79 bytes
44: got header, type 4, pathlen 0
43: paes: append_element gave us '/mnt/b/yoe/build', current ''
43: stat /mnt/b/yoe/build (+buf) (040755): msg type 3 (stat), external path /mnt/b/yoe/build, mode 040755
43: wrote 93 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 040755 uid 1000:100
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/local', current ''
43: paes: append_element gave us '/usr/local/sbin', current ''
43: paes: append_element gave us '/usr/local/sbin/cp', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/local', current ''
43: paes: append_element gave us '/usr/local/bin', current ''
43: paes: append_element gave us '/usr/local/bin/cp', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/sbin', current ''
43: paes: append_element gave us '/usr/sbin/cp', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/bin', current ''
43: paes: append_element gave us '/usr/bin/cp', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/sbin', current ''
43: paes: append_element gave us '/sbin/cp', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/cp', current ''
43: stat /bin/cp (+buf) (0100755): msg type 3 (stat), external path /bin/cp, mode 0100755
43: wrote 84 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 0100755 uid 0:0
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/cp', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/cp', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/cp', current ''
43: stat /bin/cp (+buf) (0100755): msg type 3 (stat), external path /bin/cp, mode 0100755
43: wrote 84 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 0100755 uid 0:0
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/cp', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/cp', current ''
43: pseudo_env: PSEUDO_PREFIX => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr
43: pseudo_env: PSEUDO_BINDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/bin
43: pseudo_env: PSEUDO_LIBDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/lib/pseudo/lib
43: pseudo_env: PSEUDO_LOCALSTATEDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/var/pseudo
43: pseudo_env: PSEUDO_OPTS => 
43: pseudo_env: PSEUDO_DEBUG => nfoPdDyeiVx
43: pseudo_env: PSEUDO_DISABLED => 0
45: new pid: 45 [sh]
45: close calling real syscall.
45: getcwd calling real syscall.
45: paes: append_element gave us '', current ''
45: paes: append_element gave us '/bin', current ''
45: paes: append_element gave us '/bin/cp', current ''
45: exec /bin/cp: (45) (no request)
45: setting up envp environment.
45: new pid: 45 [cp]
45: umask calling real syscall.
45: umask calling real syscall.
45: open calling real syscall.
45: fcntl calling real syscall.
45: close calling real syscall.
45: fcntl calling real syscall.
45: open calling real syscall.
45: fcntl calling real syscall.
45: close calling real syscall.
45: fcntl calling real syscall.
45: pathconf calling real syscall.
45: getcwd calling real syscall.
45: paes: append_element gave us '', current ''
45: paes: append_element gave us '/proc', current ''
45: paes: append_element gave us '/proc/filesystems', current ''
45: fopen '/proc/filesystems': fd 3 <FILE 0x55a8741055f0>
45: open /proc/filesystems [fd 3] (+buf) [dev/ino: 53/4026532070] (0100444): fcntl calling real syscall.
45: close calling real syscall.
45: fcntl calling real syscall.
45: open calling real syscall.
45: fchdir calling real syscall.
45: fchdir calling real syscall.
45: close calling real syscall.
45: msg type 1 (none), external path cp, mode 00
45: wrote 79 bytes
45: got header, type 4, pathlen 0
45: msg type 6 (open), external path /proc/filesystems, mode 0100444
45: wrote 94 bytes
45: got header, type 4, pathlen 0
45: (45) succeed
45: close /proc/filesystems [fd 3]: (45) (no request)
45: paes: append_element gave us '', current ''
45: paes: append_element gave us '/etc', current ''
45: paes: append_element gave us '/etc/selinux', current ''
45: paes: append_element gave us '/etc/selinux/config', current ''
45: new pid: 45 [cp]
45: close calling real syscall.
45: getcwd calling real syscall.
45: paes: append_element gave us '', current ''
45: paes: append_element gave us '/tmp', current ''
45: paes: append_element gave us '/tmp/test2', current ''
45: paes: append_element gave us '', current ''
45: paes: append_element gave us '/tmp', current ''
45: paes: append_element gave us '/tmp/test', current ''
45: stat /tmp/test (+buf) (0100644): fcntl calling real syscall.
45: close calling real syscall.
45: fcntl calling real syscall.
45: open calling real syscall.
45: fchdir calling real syscall.
45: fchdir calling real syscall.
45: close calling real syscall.
45: msg type 1 (none), external path cp, mode 00
45: wrote 79 bytes
45: got header, type 4, pathlen 0
45: msg type 3 (stat), external path /tmp/test, mode 0100644
45: wrote 86 bytes
45: got header, type 4, pathlen 0
45: (45) fail mode 0100644 uid 1000:1000
45: paes: append_element gave us '', current ''
45: paes: append_element gave us '/tmp', current ''
45: paes: append_element gave us '/tmp/test2', current ''
45: paes: append_element gave us '', current ''
45: paes: append_element gave us '/tmp', current ''
45: paes: append_element gave us '/tmp/test', current ''
45: openat(path /tmp/test), flags 0, stat rc 0, stat mode 100644
45: open /tmp/test [fd 3] (+buf) [dev/ino: 51/2003671] (0100044): (45) (no request)
45: fstat /tmp/test [fd 3] (+buf) [dev/ino: 51/2003671] (0100644): msg type 3 (fstat), external path /tmp/test, mode 0100644
45: wrote 86 bytes
45: got header, type 4, pathlen 0
45: (45) fail mode 0100644 uid 1000:1000
45: paes: append_element gave us '', current ''
45: paes: append_element gave us '/tmp', current ''
45: paes: append_element gave us '/tmp/test2', current ''
45: openat_creat: /tmp/test2 -> 0644
45: openat(path /tmp/test2), flags 301, stat rc 0, stat mode 100644
45: creat /tmp/test2 (+buf) (0100644): fuid: 0 msg type 6 (creat), external path /tmp/test2, mode 0100644
45: wrote 87 bytes
45: got header, type 4, pathlen 0
45: (45) succeed
45: open /tmp/test2 [fd 4] (+buf) [dev/ino: 51/2003585] (0100644): (45) (no request)
45: fstat /tmp/test2 [fd 4] (+buf) [dev/ino: 51/2003585] (0100644): msg type 3 (fstat), external path /tmp/test2, mode 0100644
45: wrote 87 bytes
45: got header, type 4, pathlen 0
45: (45) succeed mode 0100644 uid 0:0
45: close /tmp/test2 [fd 4]: (45) (no request)
45: close /tmp/test [fd 3]: (45) (no request)
45: close  [fd 0]: (45) (no request)
45: close  [fd 1]: (45) (no request)
45: close  [fd 2]: fcntl calling real syscall.
45: fcntl calling real syscall.
45: (45) (no request)
45: msg type 1 (none), external path cp, mode 00
45: wrote 79 bytes
45: got header, type 4, pathlen 0
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/tmp', current ''
43: open /tmp [fd 3] (+buf) [dev/ino: 51/1685687] (041777): (43) (no request)
43: close /tmp [fd 3]: (43) (no request)
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/ls', current ''
43: stat /bin/ls (+buf) (0100755): msg type 3 (stat), external path /bin/ls, mode 0100755
43: wrote 84 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 0100755 uid 0:0
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/ls', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/ls', current ''
43: pseudo_env: PSEUDO_PREFIX => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr
43: pseudo_env: PSEUDO_BINDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/bin
43: pseudo_env: PSEUDO_LIBDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/lib/pseudo/lib
43: pseudo_env: PSEUDO_LOCALSTATEDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/var/pseudo
43: pseudo_env: PSEUDO_OPTS => 
43: pseudo_env: PSEUDO_DEBUG => nfoPdDyeiVx
43: pseudo_env: PSEUDO_DISABLED => 0
46: new pid: 46 [sh]
46: close calling real syscall.
46: getcwd calling real syscall.
46: paes: append_element gave us '', current ''
46: paes: append_element gave us '/bin', current ''
46: paes: append_element gave us '/bin/ls', current ''
46: exec /bin/ls: (46) (no request)
46: setting up envp environment.
46: new pid: 46 [ls]
46: umask calling real syscall.
46: umask calling real syscall.
46: open calling real syscall.
46: fcntl calling real syscall.
46: close calling real syscall.
46: fcntl calling real syscall.
46: open calling real syscall.
46: fcntl calling real syscall.
46: close calling real syscall.
46: fcntl calling real syscall.
46: pathconf calling real syscall.
46: getcwd calling real syscall.
46: paes: append_element gave us '', current ''
46: paes: append_element gave us '/proc', current ''
46: paes: append_element gave us '/proc/filesystems', current ''
46: fopen '/proc/filesystems': fd 3 <FILE 0x563c5fc5d5f0>
46: open /proc/filesystems [fd 3] (+buf) [dev/ino: 53/4026532070] (0100444): fcntl calling real syscall.
46: close calling real syscall.
46: fcntl calling real syscall.
46: open calling real syscall.
46: fchdir calling real syscall.
46: fchdir calling real syscall.
46: close calling real syscall.
46: msg type 1 (none), external path ls, mode 00
46: wrote 79 bytes
46: got header, type 4, pathlen 0
46: msg type 6 (open), external path /proc/filesystems, mode 0100444
46: wrote 94 bytes
46: got header, type 4, pathlen 0
46: (46) succeed
46: close /proc/filesystems [fd 3]: (46) (no request)
46: paes: append_element gave us '', current ''
46: paes: append_element gave us '/etc', current ''
46: paes: append_element gave us '/etc/selinux', current ''
46: paes: append_element gave us '/etc/selinux/config', current ''
46: new pid: 46 [ls]
46: close calling real syscall.
46: getcwd calling real syscall.
46: paes: append_element gave us '', current ''
46: paes: append_element gave us '/tmp', current ''
46: paes: append_element gave us '/tmp/test', current ''
46: stat /tmp/test (+buf) (0100644): fcntl calling real syscall.
46: close calling real syscall.
46: fcntl calling real syscall.
46: open calling real syscall.
46: fchdir calling real syscall.
46: fchdir calling real syscall.
46: close calling real syscall.
46: msg type 1 (none), external path ls, mode 00
46: wrote 79 bytes
46: got header, type 4, pathlen 0
46: msg type 3 (stat), external path /tmp/test, mode 0100644
46: wrote 86 bytes
46: got header, type 4, pathlen 0
46: (46) fail mode 0100644 uid 1000:1000
46: paes: append_element gave us '', current ''
46: paes: append_element gave us '/tmp', current ''
46: paes: append_element gave us '/tmp/test', current ''
46: getxattr(/tmp/test [fd -1], security.selinux)
46: getxattr, name 'security.selinux'
46: combined path buffer at 0x563c5fc60460 [27 bytes]:
46: 0x000000 2f 74 6d 70  2f 74 65 73  74 00 73 65  63 75 72 69 '/tmp/test.securi'
46: 0x000010 74 79 2e 73  65 6c 69 6e  75 78 00                 'ty.selinux.'
46: get-xattr security.selinux -> /tmp/test (+buf) (0100644): msg type 3 (get-xattr), external path /tmp/test, mode 0100644
46: wrote 103 bytes
46: got header, type 4, pathlen 0
46: (46) fail
46: paes: append_element gave us '', current ''
46: paes: append_element gave us '/tmp', current ''
46: paes: append_element gave us '/tmp/test', current ''
46: getxattr(/tmp/test [fd -1], system.posix_acl_access)
46: getxattr, name 'system.posix_acl_access'
46: combined path buffer at 0x563c5fc60460 [34 bytes]:
46: 0x000000 2f 74 6d 70  2f 74 65 73  74 00 73 79  73 74 65 6d '/tmp/test.system'
46: 0x000010 2e 70 6f 73  69 78 5f 61  63 6c 5f 61  63 63 65 73 '.posix_acl_acces'
46: 0x000020 73 00                                              's.'
46: get-xattr system.posix_acl_access -> /tmp/test (+buf) (0100644): msg type 3 (get-xattr), external path /tmp/test, mode 0100644
46: wrote 110 bytes
46: got header, type 4, pathlen 0
46: (46) fail
46: paes: append_element gave us '', current ''
46: paes: append_element gave us '/tmp', current ''
46: paes: append_element gave us '/tmp/test2', current ''
46: stat /tmp/test2 (+buf) (0100644): msg type 3 (stat), external path /tmp/test2, mode 0100644
46: wrote 87 bytes
46: got header, type 4, pathlen 0
46: (46) succeed mode 0100644 uid 0:0
46: paes: append_element gave us '', current ''
46: paes: append_element gave us '/tmp', current ''
46: paes: append_element gave us '/tmp/test2', current ''
46: getxattr(/tmp/test2 [fd -1], security.selinux)
46: getxattr, name 'security.selinux'
46: combined path buffer at 0x563c5fc60460 [28 bytes]:
46: 0x000000 2f 74 6d 70  2f 74 65 73  74 32 00 73  65 63 75 72 '/tmp/test2.secur'
46: 0x000010 69 74 79 2e  73 65 6c 69  6e 75 78 00              'ity.selinux.'
46: get-xattr security.selinux -> /tmp/test2 (+buf) (0100644): msg type 3 (get-xattr), external path /tmp/test2, mode 0100644
46: wrote 104 bytes
46: got header, type 4, pathlen 0
46: (46) fail
46: paes: append_element gave us '', current ''
46: paes: append_element gave us '/tmp', current ''
46: paes: append_element gave us '/tmp/test2', current ''
46: getxattr(/tmp/test2 [fd -1], system.posix_acl_access)
46: getxattr, name 'system.posix_acl_access'
46: combined path buffer at 0x563c5fc60460 [35 bytes]:
46: 0x000000 2f 74 6d 70  2f 74 65 73  74 32 00 73  79 73 74 65 '/tmp/test2.syste'
46: 0x000010 6d 2e 70 6f  73 69 78 5f  61 63 6c 5f  61 63 63 65 'm.posix_acl_acce'
46: 0x000020 73 73 00                                           'ss.'
46: get-xattr system.posix_acl_access -> /tmp/test2 (+buf) (0100644): msg type 3 (get-xattr), external path /tmp/test2, mode 0100644
46: wrote 111 bytes
46: got header, type 4, pathlen 0
46: (46) fail
-rw-r--r-- 1 1000 1000 0 Mar  2 18:46 /tmp/test
-rw-r--r-- 1    0    0 0 Mar  2 18:46 /tmp/test2
46: close  [fd 1]: (46) (no request)
46: close  [fd 2]: fcntl calling real syscall.
46: fcntl calling real syscall.
46: (46) (no request)
46: msg type 1 (none), external path ls, mode 00
46: wrote 79 bytes
46: got header, type 4, pathlen 0
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/tmp', current ''
43: open /tmp [fd 3] (+buf) [dev/ino: 51/1685687] (041777): (43) (no request)
43: close /tmp [fd 3]: (43) (no request)
43: paes: append_element gave us '/mnt/b/yoe/build', current ''
43: stat /mnt/b/yoe/build (+buf) (040755): msg type 3 (stat), external path /mnt/b/yoe/build, mode 040755
43: wrote 93 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 040755 uid 1000:100
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/local', current ''
43: paes: append_element gave us '/usr/local/sbin', current ''
43: paes: append_element gave us '/usr/local/sbin/rm', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/local', current ''
43: paes: append_element gave us '/usr/local/bin', current ''
43: paes: append_element gave us '/usr/local/bin/rm', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/sbin', current ''
43: paes: append_element gave us '/usr/sbin/rm', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/usr', current ''
43: paes: append_element gave us '/usr/bin', current ''
43: paes: append_element gave us '/usr/bin/rm', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/sbin', current ''
43: paes: append_element gave us '/sbin/rm', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/rm', current ''
43: stat /bin/rm (+buf) (0100755): msg type 3 (stat), external path /bin/rm, mode 0100755
43: wrote 84 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 0100755 uid 0:0
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/rm', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/rm', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/rm', current ''
43: stat /bin/rm (+buf) (0100755): msg type 3 (stat), external path /bin/rm, mode 0100755
43: wrote 84 bytes
43: got header, type 4, pathlen 0
43: (43) fail mode 0100755 uid 0:0
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/rm', current ''
43: paes: append_element gave us '', current ''
43: paes: append_element gave us '/bin', current ''
43: paes: append_element gave us '/bin/rm', current ''
43: pseudo_env: PSEUDO_PREFIX => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr
43: pseudo_env: PSEUDO_BINDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/bin
43: pseudo_env: PSEUDO_LIBDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/lib/pseudo/lib
43: pseudo_env: PSEUDO_LOCALSTATEDIR => /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr/var/pseudo
43: pseudo_env: PSEUDO_OPTS => 
43: pseudo_env: PSEUDO_DEBUG => nfoPdDyeiVx
43: pseudo_env: PSEUDO_DISABLED => 0
47: new pid: 47 [sh]
47: close calling real syscall.
47: getcwd calling real syscall.
47: paes: append_element gave us '', current ''
47: paes: append_element gave us '/bin', current ''
47: paes: append_element gave us '/bin/rm', current ''
47: exec /bin/rm: (47) (no request)
47: setting up envp environment.
47: new pid: 47 [rm]
47: umask calling real syscall.
47: umask calling real syscall.
47: open calling real syscall.
47: fcntl calling real syscall.
47: close calling real syscall.
47: fcntl calling real syscall.
47: open calling real syscall.
47: fcntl calling real syscall.
47: close calling real syscall.
47: fcntl calling real syscall.
47: pathconf calling real syscall.
47: getcwd calling real syscall.
47: paes: append_element gave us '', current ''
47: paes: append_element gave us '/tmp', current ''
47: paes: append_element gave us '/tmp/test', current ''
47: stat /tmp/test (+buf) (0100644): fcntl calling real syscall.
47: close calling real syscall.
47: fcntl calling real syscall.
47: open calling real syscall.
47: fchdir calling real syscall.
47: fchdir calling real syscall.
47: close calling real syscall.
47: msg type 1 (none), external path rm, mode 00
47: wrote 79 bytes
47: got header, type 4, pathlen 0
47: msg type 3 (stat), external path /tmp/test, mode 0100644
47: wrote 86 bytes
47: got header, type 4, pathlen 0
47: (47) fail mode 0100644 uid 1000:1000
47: paes: append_element gave us '', current ''
47: paes: append_element gave us '/tmp', current ''
47: paes: append_element gave us '/tmp/test', current ''
47: may-unlink /tmp/test (+buf) (0100644): msg type 3 (may-unlink), external path /tmp/test, mode 0100644
47: wrote 86 bytes
47: got header, type 4, pathlen 0
47: (47) fail
47: unlink on </tmp/test>, not in database, no effect.
47: paes: append_element gave us '', current ''
47: paes: append_element gave us '/tmp', current ''
47: paes: append_element gave us '/tmp/test2', current ''
47: stat /tmp/test2 (+buf) (0100644): msg type 3 (stat), external path /tmp/test2, mode 0100644
47: wrote 87 bytes
47: got header, type 4, pathlen 0
47: (47) succeed mode 0100644 uid 0:0
47: paes: append_element gave us '', current ''
47: paes: append_element gave us '/tmp', current ''
47: paes: append_element gave us '/tmp/test2', current ''
47: may-unlink /tmp/test2 (+buf) (0100644): msg type 3 (may-unlink), external path /tmp/test2, mode 0100644
47: wrote 87 bytes
47: got header, type 4, pathlen 0
47: (47) succeed
47: did-unlink /tmp/test2 (+buf) (0100644): msg type 6 (did-unlink), external path /tmp/test2, mode 0100644
47: wrote 87 bytes
47: got header, type 4, pathlen 0
47: (47) succeed
47: msg type 1 (none), external path rm, mode 00
47: wrote 79 bytes
47: got header, type 4, pathlen 0
47: close  [fd 0]: (47) (no request)
47: close  [fd 1]: (47) (no request)
47: close  [fd 2]: fcntl calling real syscall.
47: fcntl calling real syscall.
47: (47) (no request)
43: msg type 1 (none), external path sh, mode 00
43: wrote 79 bytes
43: got header, type 4, pathlen 0

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

[Richard Purdie]

On Mon, 2020-03-02 at 10:49 -0800, Khem Raj wrote:
> On 3/1/20 9:05 AM, Richard Purdie wrote:
> > On Sun, 2020-03-01 at 08:20 +0000, Richard Purdie wrote:
> > > On Sun, 2020-03-01 at 00:17 -0800, Khem Raj wrote:
> > > 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?
> 
> above cmd output is exactly same as yours.
> 
> -rw-r--r-- 1 build build 0 Mar  2 18:49 /tmp/test
> Warning: PSEUDO_PREFIX unset, defaulting to 
> /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr.
> -rw-r--r-- 1 1000 1000 0 Mar  2 18:49 /tmp/test
> -rw-r--r-- 1 1000 1000 0 Mar  2 18:49 /tmp/test
> -rw-r--r-- 1    0    0 0 Mar  2 18:49 /tmp/test2

Hmm, this means the test is flawed as we need to find out how
/tmp/test2 becomes owned by 1000.1000.

Any ideas how we can simplify this down to reproduce that?

I did wonder if its coreutils-native was somehow creeping into DEPENDS
and had a different config between your two hosts which was causing
different behaviour but I'd need to check into whether that happens.

Any other ideas why the behaviour difference or how to reproduce it?

Cheers,

Richard

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

[Khem Raj]

On 3/2/20 1:08 PM, Richard Purdie wrote:
> On Mon, 2020-03-02 at 10:49 -0800, Khem Raj wrote:
>> On 3/1/20 9:05 AM, Richard Purdie wrote:
>>> On Sun, 2020-03-01 at 08:20 +0000, Richard Purdie wrote:
>>>> On Sun, 2020-03-01 at 00:17 -0800, Khem Raj wrote:
>>>> 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?
>>
>> above cmd output is exactly same as yours.
>>
>> -rw-r--r-- 1 build build 0 Mar  2 18:49 /tmp/test
>> Warning: PSEUDO_PREFIX unset, defaulting to
>> /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-native/usr.
>> -rw-r--r-- 1 1000 1000 0 Mar  2 18:49 /tmp/test
>> -rw-r--r-- 1 1000 1000 0 Mar  2 18:49 /tmp/test
>> -rw-r--r-- 1    0    0 0 Mar  2 18:49 /tmp/test2
> 
> Hmm, this means the test is flawed as we need to find out how
> /tmp/test2 becomes owned by 1000.1000.
> 
> Any ideas how we can simplify this down to reproduce that?
> 


Even on baremetal ubuntu 18.04 I am seeing

dlm-4.0.9: dlm: /usr/lib/libdlmcontrol.so is owned by uid 3004, which is 
the same as the user running bitbake. This may be due to host contamination
dlm: /usr/lib/libdlm_lt.so is owned by uid 3004, which is the same as 
the user running bitbake. This may be due to host contamination
dlm: /usr/lib/libdlm.so is owned by uid 3004, which is the same as the 
user running bitbake. This may be due to host contamination 
[host-user-contaminated]
dlm-4.0.9: dlm: /usr/lib/libdlmcontrol.so.3 is owned by uid 3004, which 
is the same as the user running bitbake. This may be due to host 
contamination
dlm: /usr/lib/libdlm_lt.so.3 is owned by uid 3004, which is the same as 
the user running bitbake. This may be due to host contamination
dlm: /usr/lib/libdlm.so.3 is owned by uid 3004, which is the same as the 
user running bitbake. This may be due to host contamination 
[host-user-contaminated]


this might be again a dlm issue to fix.  but perhaps a good one to try 
if AB system can build it without these QA diagnostics.

dlm is in meta-networking.

> I did wonder if its coreutils-native was somehow creeping into DEPENDS
> and had a different config between your two hosts which was causing
> different behaviour but I'd need to check into whether that happens.
> 
> Any other ideas why the behaviour difference or how to reproduce it?
> 

can you promote host-user-contaminated form QA warning to QA error in 
poky and see if builds fail ?

> Cheers,
> 
> Richard
> 
> 
> 
> 

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

[Richard Purdie]

On Mon, 2020-03-02 at 13:33 -0800, Khem Raj wrote:
> 
> On 3/2/20 1:08 PM, Richard Purdie wrote:
> > On Mon, 2020-03-02 at 10:49 -0800, Khem Raj wrote:
> > > On 3/1/20 9:05 AM, Richard Purdie wrote:
> > > > On Sun, 2020-03-01 at 08:20 +0000, Richard Purdie wrote:
> > > > > On Sun, 2020-03-01 at 00:17 -0800, Khem Raj wrote:
> > > > > 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?
> > > 
> > > above cmd output is exactly same as yours.
> > > 
> > > -rw-r--r-- 1 build build 0 Mar  2 18:49 /tmp/test
> > > Warning: PSEUDO_PREFIX unset, defaulting to
> > > /mnt/b/yoe/build/./tmp/sysroots-components/x86_64/pseudo-
> > > native/usr.
> > > -rw-r--r-- 1 1000 1000 0 Mar  2 18:49 /tmp/test
> > > -rw-r--r-- 1 1000 1000 0 Mar  2 18:49 /tmp/test
> > > -rw-r--r-- 1    0    0 0 Mar  2 18:49 /tmp/test2
> > 
> > Hmm, this means the test is flawed as we need to find out how
> > /tmp/test2 becomes owned by 1000.1000.
> > 
> > Any ideas how we can simplify this down to reproduce that?
> > 
> 
> Even on baremetal ubuntu 18.04 I am seeing
> 
> dlm-4.0.9: dlm: /usr/lib/libdlmcontrol.so is owned by uid 3004, which is 
> the same as the user running bitbake. This may be due to host contamination
> dlm: /usr/lib/libdlm_lt.so is owned by uid 3004, which is the same as 
> the user running bitbake. This may be due to host contamination
> dlm: /usr/lib/libdlm.so is owned by uid 3004, which is the same as the 
> user running bitbake. This may be due to host contamination 
> [host-user-contaminated]
> dlm-4.0.9: dlm: /usr/lib/libdlmcontrol.so.3 is owned by uid 3004, which 
> is the same as the user running bitbake. This may be due to host 
> contamination
> dlm: /usr/lib/libdlm_lt.so.3 is owned by uid 3004, which is the same as 
> the user running bitbake. This may be due to host contamination
> dlm: /usr/lib/libdlm.so.3 is owned by uid 3004, which is the same as the 
> user running bitbake. This may be due to host contamination 
> [host-user-contaminated]
> 
> this might be again a dlm issue to fix.  but perhaps a good one to
> try  if AB system can build it without these QA diagnostics.
> 
> dlm is in meta-networking.

That could well be a dlm recipe bug. I'm more interested in the ones
which reproducibly break on one machine but work on another.

> > I did wonder if its coreutils-native was somehow creeping into
> > DEPENDS
> > and had a different config between your two hosts which was causing
> > different behaviour but I'd need to check into whether that
> > happens.
> > 
> > Any other ideas why the behaviour difference or how to reproduce
> > it?
> > 
> 
> can you promote host-user-contaminated form QA warning to QA error
> in poky and see if builds fail ?

As its already a warning, we'd see it on the autobuilder. *Any* warning
turns the build orange rather than green. We don't any warnings in core
builds, we fixed them all. This is why I know its not happening on the
autobuilder...

Cheers,

Richard