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

[dS Jenkins]

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

Changes:

[andreas.fenkart] watchdog: double the 1-min cpu overload before triggering a reboot

------------------------------------------
[...truncated 198.09 KB...]
WARNING: rpm-1_4.14.1-r0 do_package_qa: QA Issue: rpm: /rpm-locale-nb/usr/share/locale/nb/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]
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-dev/usr/include/rpm/rpmstrpool.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/rpmspec.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/rpmurl.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/rpmte.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/argv.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/rpmcli.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/rpmts.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/rpmarchive.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/rpmpol.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/rpmsign.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/rpmfiles.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/rpmbuild.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/rpmsw.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/rpmprob.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/rpmio.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/rpmfileutil.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/rpmlib.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/header.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/rpmlog.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/rpmvf.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/rpmfi.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/rpmbase64.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/rpmpgp.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/rpmsq.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/rpmdb.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/rpmkeyring.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/rpmds.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/rpmps.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/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-doc/usr/share/man/man1/gendiff.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/sk/man8/rpm.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/ru/man8/rpm2cpio.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/ru/man8/rpm.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/ko/man8/rpm2cpio.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/ko/man8/rpm.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/pl/man1/gendiff.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/pl/man8/rpmgraph.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/pl/man8/rpm2cpio.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/pl/man8/rpmbuild.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/pl/man8/rpm.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/pl/man8/rpmdeps.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/fr/man8/rpm.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/ja/man8/rpmgraph.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/ja/man8/rpm2cpio.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/ja/man8/rpmbuild.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/ja/man8/rpm.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/man8/rpmsign.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/man8/rpmgraph.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/man8/rpmkeys.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/man8/rpmspec.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/man8/rpm2cpio.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/man8/rpmbuild.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/man8/rpm.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/man8/rpm-misc.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/man8/rpm-plugin-systemd-inhibit.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/man8/rpmdb.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
rpm: /rpm-doc/usr/share/man/man8/rpmdeps.8 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 lttng-ust-2_2.10.1-r0: task do_package_qa: Succeeded
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_package_write_ipk: Succeeded
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-vi/usr/share/locale/vi/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-sr+latin/usr/share/locale/sr at latin/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-te/usr/share/locale/te/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 rpm-1_4.14.1-r0: task do_package_qa: Succeeded
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_package_write_ipk: Succeeded
NOTE: recipe rpm-1_4.14.1-r0: task do_package_write_ipk: Succeeded
NOTE: Tasks Summary: Attempted 4001 tasks of which 3983 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 51 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 jin at developer.digitalstrom.org
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 jean.visagie at digitalstrom.com