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

[dS Jenkins]

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

Changes:

[jin] Updated rescue testing bblayers.conf to match Yocto 2.5.1 setup

------------------------------------------
[...truncated 95.71 KB...]
rpm: /rpm-dev/usr/include/rpm/rpmutil.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-dev/usr/include/rpm/rpmmacro.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-dev/usr/include/rpm/rpmtag.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-dev/usr/include/rpm/rpmcallback.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-dev/usr/include/rpm/rpmtypes.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-dev/usr/include/rpm/rpmfc.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-dev/usr/include/rpm/rpmtd.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-dev/usr/include/rpm/rpmstring.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-dev/usr/lib/librpm.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-dev/usr/lib/librpmbuild.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-dev/usr/lib/librpmsign.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-dev/usr/lib/librpmio.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-dev/usr/lib/pkgconfig/rpm.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]
WARNING: rpm-1_4.14.1-r0 do_package_qa: QA Issue: rpm: /rpm-locale-pl/usr/share/locale/pl/LC_MESSAGES/rpm.mo 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 libdsm-api-git-r2: task do_packagedata: Succeeded
NOTE: Running task 3936 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-api/libdsm-api_git.bb:do_package_qa)
WARNING: rpm-1_4.14.1-r0 do_package_qa: QA Issue: rpm: /rpm/usr/bin/rpmsign is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/bin/rpmbuild is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/bin/rpmdb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/bin/rpmspec is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/bin/gendiff is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/bin/rpm2archive is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/bin/rpm2cpio is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/bin/rpm is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/bin/rpmkeys is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/bin/rpmquery is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/bin/rpmgraph is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/bin/rpmverify is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/librpmsign.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/librpm.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/librpmbuild.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/librpmbuild.so.8.0.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/librpm.so.8.0.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/librpmsign.so.8.0.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/librpmio.so.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/librpmio.so.8.0.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm-plugins/ima.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm-plugins/syslog.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm-plugins/systemd_inhibit.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm-plugins/prioreset.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/elfdeps is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/rpm.supp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/rpmdeps is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/brp-strip-shared is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/python-macro-helper is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/script.req is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/rpm.daily is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/debugedit is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/tgpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/brp-strip-comment-note is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/check-prereqs is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/config.sub is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/find-lang.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/rpm.log is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/pkgconfigdeps.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/rpmpopt-4.14.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/brp-strip-static-archive is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/perl.req is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/check-rpaths-worker is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/rpm2cpio.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/brp-strip is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/check-buildroot is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/ocaml-find-provides.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fontconfig.prov is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/macros.python is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/brp-python-hardlink is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/metainfo.prov is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/brp-python-bytecompile is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/libtooldeps.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/desktop-file.prov is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/macros.php is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/sepdebugcrcfix is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/mkinstalldirs is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/macros.perl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/ocaml-find-requires.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/mono-find-provides is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/find-debuginfo.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/find-provides is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/config.guess is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/pythondeps.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/rpmrc is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/brp-compress is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/rpmdb_loadcvt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/debuginfo.prov is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/find-requires is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/brp-java-gcjcompile is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/check-rpaths is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/pythondistdeps.py is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/mono-find-requires is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/check-files is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/perl.prov is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fileattrs/pkgconfig.attr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fileattrs/debuginfo.attr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fileattrs/libtool.attr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fileattrs/perl.attr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fileattrs/script.attr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fileattrs/perllib.attr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fileattrs/ocaml.attr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fileattrs/python.attr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fileattrs/font.attr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fileattrs/elf.attr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fileattrs/mono.attr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fileattrs/desktop.attr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/fileattrs/metainfo.attr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/sparcv8-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/ppc8260-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/sparcv9-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/ppc64iseries-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/s390x-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/mipsr6-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/athlon-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/aarch64-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/ppc64-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/riscv64-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/ppcpseries-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/i686-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/sparc-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/alpha-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/armv7l-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/x86_64-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/armv7hnl-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/mips64-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/sparc64-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/sh-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/ppc64p7-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/m68k-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/geode-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/sh3-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/pentium3-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/i386-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/armv5tl-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/mipsr6el-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/ia32e-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/mips64el-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/mips64r6el-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/noarch-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/ppc64le-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/i586-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/armv3l-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/armv7hl-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/mips-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/ia64-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/alphaev67-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/alphaev6-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/ppc64pseries-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/armv6hl-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/armv6l-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/alphaev56-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/armv4l-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/ppciseries-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/sh4-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/mipsel-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/ppc32dy4-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/armv5tejl-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/i486-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/s390-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/ppc-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/amd64-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/alphaev5-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/armv4b-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/armv5tel-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/sparc64v-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/sparcv9v-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/mips64r6-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/sh4a-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/alphapca56-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/ppc8560-linux/macros is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm/usr/lib/rpm/platform/pentium4-linux/macros 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: rpm-1_4.14.1-r0 do_package_qa: QA Issue: rpm: /rpm-locale-pt/usr/share/locale/pt/LC_MESSAGES/rpm.mo 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: rpm-1_4.14.1-r0 do_package_qa: QA Issue: rpm: /rpm-locale-ja/usr/share/locale/ja/LC_MESSAGES/rpm.mo 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: rpm-1_4.14.1-r0 do_package_qa: QA Issue: rpm: /rpm-locale-cmn/usr/share/locale/cmn/LC_MESSAGES/rpm.mo 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: rpm-1_4.14.1-r0 do_package_qa: QA Issue: rpm: /rpm-locale-tr/usr/share/locale/tr/LC_MESSAGES/rpm.mo 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 libdsm-api-git-r2: task do_package_qa: Started
WARNING: libdsm-api-git-r2 do_package_qa: QA Issue: libdsm-api: /libdsm-api/usr/lib/libdsm-api-v2.so.3.4.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]
WARNING: libdsm-api-git-r2 do_package_qa: QA Issue: libdsm-api: /libdsm-api-lua/usr/lib/lua/5.2/dsmapi2.so 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: libdsm-api-git-r2 do_package_qa: QA Issue: libdsm-api: /libdsm-api-utils/usr/bin/num_bus_members 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: libdsm-api-git-r2 do_package_qa: QA Issue: libdsm-api: /libdsm-api-python/usr/bin/dsm-api-logger.py is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libdsm-api: /libdsm-api-python/usr/lib/python2.7/site-packages/dsmapi2/dsmapi2.py is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libdsm-api: /libdsm-api-python/usr/lib/python2.7/site-packages/dsmapi2/__init__.py is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libdsm-api: /libdsm-api-python/usr/lib/python2.7/site-packages/dsmapi2/_dsmapi2.so 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 rpm-1_4.14.1-r0: task do_package_qa: Succeeded
NOTE: Running task 3937 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-api/libdsm-api_git.bb:do_package_write_ipk)
NOTE: recipe libdsm-api-git-r2: task do_package_write_ipk: Started
NOTE: recipe libdsm-api-git-r2: task do_package_qa: Succeeded
NOTE: Running task 3945 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/ds485p/ds485p_git.bb:do_install)
NOTE: recipe ds485p-git-r5: task do_install: Started
NOTE: recipe ds485p-git-r5: task do_install: Succeeded
NOTE: Running task 3946 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/ds485p/ds485p_git.bb:do_populate_sysroot)
NOTE: recipe ds485p-git-r5: task do_populate_sysroot: Started
NOTE: recipe libsolv-0.6.33-r0: task do_configure: Succeeded
NOTE: Running task 3947 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/ds485p/ds485p_git.bb:do_package)
NOTE: recipe ds485p-git-r5: task do_package: Started
NOTE: recipe ds485p-git-r5: task do_populate_sysroot: Succeeded
NOTE: Running task 3948 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-extended/libsolv/libsolv_0.6.33.bb:do_compile)
NOTE: recipe libsolv-0.6.33-r0: task do_compile: Started
NOTE: recipe rpm-1_4.14.1-r0: task do_package_write_ipk: Succeeded
NOTE: Running task 3949 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/rpm/rpm_4.14.1.bb:do_rm_work)
NOTE: recipe libdsm-api-git-r2: task do_package_write_ipk: Succeeded
NOTE: Running task 3950 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-api/libdsm-api_git.bb:do_rm_work)
NOTE: recipe libdsm-api-git-r2: task do_rm_work: Started
NOTE: recipe rpm-1_4.14.1-r0: task do_rm_work: Started
NOTE: recipe rpm-1_4.14.1-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 3951 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/rpm/rpm_4.14.1.bb:do_rm_work_all)
NOTE: Running noexec task 3952 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/rpm/rpm_4.14.1.bb:do_build)
NOTE: Running task 3961 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install)
NOTE: recipe libdsm-api-git-r2: task do_rm_work: Succeeded
NOTE: Running noexec task 3962 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-api/libdsm-api_git.bb:do_rm_work_all)
NOTE: Running noexec task 3963 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-api/libdsm-api_git.bb:do_build)
NOTE: Running task 3965 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libpagekite/libpagekite_git.bb:do_prepare_recipe_sysroot)
NOTE: recipe rescue-install-git-r2: task do_install: Started
NOTE: recipe libpagekite-git-r4: task do_prepare_recipe_sysroot: 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.9384)
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.9384
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-core/glibc/glibc_2.27.bb:do_populate_sysroot', 'virtual:native:/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot', 'virtual:native:/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.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']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['quilt-native', 'glibc', 'pseudo-native', 'u-boot-mkimage-native', 'gcc-cross-arm', 'gcc-runtime', 'mpfr-native', 'texinfo-dummy-native', 'libtool-native', 'flex-native', 'xz-native', 'automake-native', 'binutils-cross-arm', 'linux-libc-headers', 'libmpc-native', 'gmp-native', 'gnu-config-native', 'autoconf-native', 'zlib-native', 'openssl-native', 'libgcc', 'gettext-minimal-native', 'bison-native', 'coreutils-native', 'm4-native', 'pkgconfig-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.9384: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.9384)
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: recipe lttng-ust-2_2.10.1-r0: task do_package: Succeeded
NOTE: recipe libpagekite-git-r4: task do_prepare_recipe_sysroot: Succeeded
NOTE: recipe dsid-tools-git-r5: task do_configure: Succeeded
NOTE: recipe libsolv-0.6.33-r0: task do_compile: Succeeded
NOTE: recipe ds485p-git-r5: task do_package: Succeeded
NOTE: recipe dsm-config-update-git-r2: task do_configure: Succeeded
NOTE: recipe dsm-firmware-upgrade-git-r1: task do_configure: Succeeded
NOTE: Tasks Summary: Attempted 3966 tasks of which 3933 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 44 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 Krzysztof.Michonski at digitalstrom.com
Not sending mail to unregistered user andreas.fenkart at dev.digitalstrom.org
Not sending mail to unregistered user jin at developer.digitalstrom.org
Not sending mail to unregistered user jean.visagie at digitalstrom.com