[dss-merge-requests] Build failed in Jenkins: yocto #3178

Tue Aug 13 13:58:40 CEST 2019

See <http://dsjenkins.cloudapp.net/jenkins/job/yocto/3178/display/redirect?page=changes>

Changes:

[Krzysztof.Michonski] rootfs: kernel: update srcrev

[Marcin Poplawski] Add panasonic ui notification page to fieldtest

------------------------------------------
[...truncated 35.51 KB...]
NOTE: recipe linux-5.1.7-5.1.7-r0: task do_fetch: Started
NOTE: Running task 3197 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-fw-upgrade/dsm-firmware-upgrade_git.bb:do_compile)
NOTE: Running task 3504 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-fw-upgrade/dsm-config-update_git.bb:do_compile)
NOTE: recipe dsm-firmware-upgrade-git-r1: task do_compile: Started
NOTE: Running task 3692 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-extended/libsolv/libsolv_0.6.33.bb:do_install)
NOTE: recipe dsm-config-update-git-r2: task do_compile: Started
NOTE: Running task 3895 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsid-tools/dsid-tools_git.bb:do_compile)
NOTE: Running task 3906 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-kernel/lttng/lttng-ust_2.10.1.bb:do_packagedata)
NOTE: Running task 3933 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/ds485p/ds485p_git.bb:do_packagedata)
NOTE: Running task 3942 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install)
NOTE: recipe dsid-tools-git-r5: task do_compile: Started
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_packagedata: Started
NOTE: recipe ds485p-git-r5: task do_packagedata: Started
NOTE: recipe rescue-install-git-r2: task do_install: Started
NOTE: recipe libsolv-0.6.33-r0: task do_install: Started
NOTE: recipe ds485p-git-r5: task do_packagedata: Succeeded
NOTE: Running task 3948 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libpagekite/libpagekite_git.bb:do_configure)
NOTE: recipe libpagekite-git-r4: task do_configure: Started
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_packagedata: Succeeded
NOTE: Running task 3949 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-kernel/lttng/lttng-ust_2.10.1.bb:do_package_qa)
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_package_qa: Started
ERROR: rescue-install-git-r2 do_install: Function failed: do_install (log file is located at /home/****/workspace/yocto/poky-devel-nopkg-build/build/work/dss20-poky-linux-gnueabi/rescue-install/git-r2/temp/log.do_install.2290)
ERROR: Logfile of failure stored in: /home/****/workspace/yocto/poky-devel-nopkg-build/build/work/dss20-poky-linux-gnueabi/rescue-install/git-r2/temp/log.do_install.2290
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['virtual:native:/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb:do_populate_sysroot', 'virtual:native:/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/gcc/gcc-cross_7.3.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/gcc/gcc-runtime_7.3.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-core/glibc/glibc_2.27.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['u-boot-mkimage-native', 'pseudo-native', 'gcc-cross-arm', 'gcc-runtime', 'glibc', 'quilt-native', 'linux-libc-headers', 'openssl-native', 'autoconf-native', 'zlib-native', 'texinfo-dummy-native', 'binutils-cross-arm', 'libmpc-native', 'flex-native', 'mpfr-native', 'gmp-native', 'gnu-config-native', 'automake-native', 'libtool-native', 'xz-native', 'libgcc', 'pkgconfig-native', 'm4-native', 'bison-native', 'gettext-minimal-native', 'coreutils-native', 'attr-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| awk: fatal: cannot open file `/home/****/workspace/yocto/poky-devel-nopkg-build/build/work/dss20-poky-linux-gnueabi/rescue-install/git-r2/git/dss20/rescue-initramfs/desc' for reading (No such file or directory)
| WARNING: /home/****/workspace/yocto/poky-devel-nopkg-build/build/work/dss20-poky-linux-gnueabi/rescue-install/git-r2/temp/run.do_install.2290:1 exit 2 from 'KN_IMG="$(awk -F= '/kernel/ {print $2;}' /home/****/workspace/yocto/poky-devel-nopkg-build/build/work/dss20-poky-linux-gnueabi/rescue-install/git-r2/git/dss20/rescue-initramfs/desc)"'
| ERROR: Function failed: do_install (log file is located at /home/****/workspace/yocto/poky-devel-nopkg-build/build/work/dss20-poky-linux-gnueabi/rescue-install/git-r2/temp/log.do_install.2290)
NOTE: recipe rescue-install-git-r2: task do_install: Failed
ERROR: Task (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install) failed with exit code '1'
NOTE: Running task 3950 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-kernel/lttng/lttng-ust_2.10.1.bb:do_package_write_ipk)
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_package_write_ipk: Started
WARNING: lttng-ust-2_2.10.1-r0 do_package_qa: QA Issue: lttng-ust: /lttng-ust-bin/usr/bin/lttng-gen-tp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: lttng-ust-2_2.10.1-r0 do_package_qa: QA Issue: lttng-ust: /lttng-ust-doc/usr/share/doc/lttng-ust/java-agent.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-doc/usr/share/doc/lttng-ust/ChangeLog is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-doc/usr/share/doc/lttng-ust/README.md is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: lttng-ust-2_2.10.1-r0 do_package_qa: QA Issue: lttng-ust: /lttng-ust-dev/usr/include/lttng/align.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/tracepoint-rcu.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-endian.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-tracer.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/lttng-ust-tracelog.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-version.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/tracepoint.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-getcpu.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-abi.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-tracepoint-event-nowrite.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/tracelog.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-ctl.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-compiler.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-tracepoint-event-write.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-elf.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-tracepoint-event-reset.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-error.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-tracepoint-event.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/lttng-ust-tracef.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-config.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/tracepoint-types.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ringbuffer-config.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-clock.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/tracepoint-event.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-events.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/bug.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/tracef.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ringbuffer-abi.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-tracepoint.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-ctl.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-dl.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-cyg-profile.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-fd.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-libc-wrapper.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-cyg-profile-fast.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-fork.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-pthread-wrapper.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/pkgconfig/lttng-ust.pc is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: recipe dsid-tools-git-r5: task do_compile: Succeeded
WARNING: lttng-ust-2_2.10.1-r0 do_package_qa: QA Issue: lttng-ust: /lttng-ust/usr/lib/liblttng-ust-cyg-profile-fast.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-libc-wrapper.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-fd.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-cyg-profile-fast.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-pthread-wrapper.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-fork.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-pthread-wrapper.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-fd.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-fork.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-dl.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-libc-wrapper.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-tracepoint.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-cyg-profile.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-cyg-profile.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-ctl.so.4.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-tracepoint.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-ctl.so.4 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-dl.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: recipe libsolv-0.6.33-r0: task do_install: Succeeded
WARNING: lttng-ust-2_2.10.1-r0 do_package_qa: QA Issue: lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/snprintf/patient_write.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/snprintf/snprintf.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/snprintf/wcio.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/snprintf/wsetup.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/snprintf/local.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/snprintf/core.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/snprintf/fvwrite.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/snprintf/mbrtowc_sb.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/snprintf/fflush.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/snprintf/various.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/snprintf/vfprintf.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/snprintf/fvwrite.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/snprintf/fileext.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-cyg-profile/lttng-ust-cyg-profile-fast.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-cyg-profile/lttng-ust-cyg-profile.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-cyg-profile/lttng-ust-cyg-profile-fast.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-cyg-profile/lttng-ust-cyg-profile.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-fd/lttng-ust-fd.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-ctl/ustctl.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-dl/lttng-ust-dl.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-dl/ust_dl.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-filter-validator.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ust-statedump-provider.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-filter-specialize.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-filter.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-getcpu.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ring-buffer-metadata-client.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/clock.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-cpu-id.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/compat.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-hash-helper.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-vpid.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-events.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-tracer-core.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-filter.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ust-statedump.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ust-elf.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-probes.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ring-buffer-client.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/tracelog.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-pthread-id.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/jhash.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-vtid.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-rb-clients.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ust-statedump.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-procname.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/getenv.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/ust-core.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/tracepoint-internal.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/perf_event.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-clock.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ust-comm.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ust-dynamic-type.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/string-utils.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/string-utils.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-perf-counters.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/getenv.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ust-abi.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/ust_lib.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/tracepoint-weak-test.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-ip.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/tracepoint.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-provider.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/error.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/tracef.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/filter-bytecode.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-filter-interpreter.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/ust-comm.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/ust-fd.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/share.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/usterr-signal-safe.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/helper.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-dlfcn.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/lttng-ust-tracelog.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/tracepoint.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-context-provider.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-abi.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-ctl.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-elf.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-error.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-tracepoint-event.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/lttng-ust-tracef.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/tracepoint-types.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ringbuffer-config.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-dynamic-type.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-events.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-tid.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/backend_internal.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/ring_buffer_frontend.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/vatomic.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/shm_types.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/backend_types.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/getcpu.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/frontend.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/rb-init.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/shm.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/backend.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/frontend_internal.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/shm_internal.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/smp.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/shm.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/ring_buffer_backend.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/frontend_types.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/smp.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/frontend_api.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-comm/lttng-ust-fd-tracker.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-comm/lttng-ust-comm.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-libc-wrapper/ust_libc.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-libc-wrapper/lttng-ust-malloc.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-libc-wrapper/ust_pthread.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-libc-wrapper/lttng-ust-pthread.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-fork/ustfork.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-libc-wrapper.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-fd.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-cyg-profile-fast.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-pthread-wrapper.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-fork.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-dl.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-tracepoint.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-cyg-profile.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-ctl.so.4.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: recipe dsm-config-update-git-r2: task do_compile: Succeeded
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_package_qa: Succeeded
NOTE: recipe dsm-firmware-upgrade-git-r1: task do_compile: Succeeded
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_package_write_ipk: Succeeded
NOTE: recipe linux-5.1.7-5.1.7-r0: task do_fetch: Succeeded
NOTE: recipe libpagekite-git-r4: task do_configure: Succeeded
NOTE: Tasks Summary: Attempted 3950 tasks of which 3939 didn't need to be rerun and 1 failed.
NOTE: No commit since BUILDHISTORY_COMMIT != '1'
NOTE: Syncing deploy/images.

Summary: 1 task failed:
  /home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install
Summary: There were 5 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

bitbake returned 1, manual interaction required!

Build step 'Execute shell' marked build as failure
Not sending mail to unregistered user andreas.fenkart at dev.digitalstrom.org
Not sending mail to unregistered user jean.visagie at digitalstrom.com
Not sending mail to unregistered user jin at developer.digitalstrom.org
Not sending mail to unregistered user Krzysztof.Michonski at digitalstrom.com