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

[dS Jenkins]

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

Changes:

[jin] Fix rs_upload class in production

------------------------------------------
[...truncated 35.20 KB...]
NOTE: Running noexec task 3191 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 3192 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-api/libdsm-api_git.bb:do_build)
NOTE: Running task 3200 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-fw-upgrade/dsm-firmware-upgrade_git.bb:do_install)
NOTE: recipe linux-5.1.7-5.1.7-r0: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 3508 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-fw-upgrade/dsm-config-update_git.bb:do_install)
NOTE: recipe dsm-firmware-upgrade-git-r1: task do_install: Started
NOTE: Running task 3700 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-extended/libsolv/libsolv_0.6.33.bb:do_package_qa)
NOTE: Running task 3701 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-extended/libsolv/libsolv_0.6.33.bb:do_package_write_ipk)
NOTE: recipe dsm-config-update-git-r2: task do_install: Started
NOTE: Running task 3905 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsid-tools/dsid-tools_git.bb:do_install)
NOTE: Running task 3957 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install)
NOTE: recipe libsolv-0.6.33-r0: task do_package_write_ipk: Started
NOTE: Running task 3963 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_configure)
NOTE: recipe libsolv-0.6.33-r0: task do_package_qa: Started
NOTE: recipe rescue-install-git-r2: task do_install: Started
NOTE: recipe libupnp-1.6.19-r2: task do_configure: Started
NOTE: recipe dsid-tools-git-r5: task do_install: Started
NOTE: recipe dsm-config-update-git-r2: task do_install: Succeeded
NOTE: Running task 3964 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-fw-upgrade/dsm-config-update_git.bb:do_populate_sysroot)
NOTE: recipe dsm-config-update-git-r2: task do_populate_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.2230)
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.2230
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/gcc/gcc-runtime_7.3.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', '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/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']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['gcc-runtime', 'pseudo-native', 'gcc-cross-arm', 'u-boot-mkimage-native', 'quilt-native', 'glibc', 'linux-libc-headers', 'libgcc', 'openssl-native', 'texinfo-dummy-native', 'binutils-cross-arm', 'libmpc-native', 'gmp-native', 'mpfr-native', 'gnu-config-native', 'xz-native', 'autoconf-native', 'automake-native', 'zlib-native', 'libtool-native', 'flex-native', 'pkgconfig-native', 'bison-native', 'coreutils-native', 'gettext-minimal-native', 'm4-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.2230: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.2230)
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 3965 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-fw-upgrade/dsm-config-update_git.bb:do_package)
NOTE: recipe dsm-firmware-upgrade-git-r1: task do_install: Succeeded
WARNING: libsolv-0.6.33-r0 do_package_qa: QA Issue: libsolv: /libsolv/usr/lib/libsolv.so.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: libsolv-0.6.33-r0 do_package_qa: QA Issue: libsolv: /libsolvext/usr/lib/libsolvext.so.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 dsid-tools-git-r5: task do_install: Succeeded
NOTE: recipe dsm-config-update-git-r2: task do_package: Started
NOTE: recipe dsm-config-update-git-r2: task do_populate_sysroot: Succeeded
WARNING: libsolv-0.6.33-r0 do_package_qa: QA Issue: libsolv: /libsolv-dbg/usr/bin/.debug/mergesolv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/bin/.debug/rpms2solv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/bin/.debug/testsolv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/bin/.debug/installcheck is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/bin/.debug/repomdxml2solv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/bin/.debug/dumpsolv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/bin/.debug/rpmmd2solv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/bin/.debug/deltainfoxml2solv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/bin/.debug/updateinfoxml2solv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/bin/.debug/rpmdb2solv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/repo_rpmmd.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/solv_xmlparser.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/repo_deltainfoxml.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/repo_rpmmd.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/repo_repomdxml.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/tools_util.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/repo_rpmdb.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/repodata_diskusage.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/pool_fileconflicts.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/solv_xfopen.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/pool_parserpmrichdep.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/testcase.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/solv_xfopen.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/repo_deltainfoxml.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/pool_parserpmrichdep.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/repodata_diskusage.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/solv_xmlparser.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/repo_updateinfoxml.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/repo_updateinfoxml.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/repo_rpmdb_bdb.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/repo_rpmdb.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/testcase.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/ext/repo_repomdxml.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/selection.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/sha1.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/repo_write.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/rules.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/solverdebug.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/bitmap.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/util.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/poolarch.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/solver_util.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/solver_private.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/transaction.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/poolarch.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/repo.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/poolid.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/userinstalled.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/solvversion.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/poolvendor.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/policy.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/selection.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/dataiterator.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/rules.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/policy.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/strpool.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/pool.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/solverdebug.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/repopage.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/md5.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/util.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/poolid.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/chksum.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/md5.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/sha1.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/repo.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/cplxdeps.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/fileprovides.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/repo_solv.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/knownid.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/repo_solv.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/hash.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/suse.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/sha2.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/repodata.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/solvable.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/dirpool.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/evr.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/bitmap.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/cplxdeps.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/solvable.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/strpool.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/evr.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/repopage.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/pool.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/diskusage.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/pooltypes.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/repopack.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/repodata.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/repo_write.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/sha2.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/solver.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/dirpool.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/queue.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/chksum.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/problems.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/problems.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/solver.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/cleandeps.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/poolvendor.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/order.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/queue.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/src/transaction.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/tools/deltainfoxml2solv.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/tools/common_write.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/tools/rpms2solv.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/tools/dumpsolv.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/tools/rpmdb2solv.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/tools/common_write.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/tools/updateinfoxml2solv.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/tools/mergesolv.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/tools/testsolv.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/tools/repomdxml2solv.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/tools/rpmmd2solv.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/git/tools/installcheck.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/src/debug/libsolv/0.6.33-r0/build/src/solvversion.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/lib/.debug/libsolvext.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dbg/usr/lib/.debug/libsolv.so.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: libsolv-0.6.33-r0 do_package_qa: QA Issue: libsolv: /libsolv-tools/usr/bin/mergesolv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-tools/usr/bin/rpms2solv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-tools/usr/bin/repo2solv.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-tools/usr/bin/testsolv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-tools/usr/bin/installcheck is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-tools/usr/bin/repomdxml2solv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-tools/usr/bin/dumpsolv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-tools/usr/bin/rpmmd2solv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-tools/usr/bin/deltainfoxml2solv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-tools/usr/bin/updateinfoxml2solv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-tools/usr/bin/rpmdb2solv 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: libsolv-0.6.33-r0 do_package_qa: QA Issue: libsolv: /libsolv-dev/usr/share/cmake/Modules/FindLibSolv.cmake is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/bitmap.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/repo_rpmmd.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/transaction.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/poolarch.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/repo.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/policy.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/selection.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/repo_deltainfoxml.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/dataiterator.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/rules.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/strpool.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/pool.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/solverdebug.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/util.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/poolid.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/chksum.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/tools_util.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/solvversion.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/knownid.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/repo_solv.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/hash.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/repo_rpmdb.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/evr.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/solvable.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/pool_parserpmrichdep.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/testcase.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/solv_xfopen.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/pooltypes.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/repodata.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/repo_write.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/dirpool.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/repo_updateinfoxml.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/problems.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/pool_fileconflicts.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/solver.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/poolvendor.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/repo_repomdxml.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/include/solv/queue.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/lib/libsolv.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/lib/libsolvext.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/lib/pkgconfig/libsolv.pc is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-dev/usr/lib/pkgconfig/libsolvext.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: libsolv-0.6.33-r0 do_package_qa: QA Issue: libsolv: /libsolv-doc/usr/share/man/man1/dumpsolv.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man1/rpmdb2solv.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man1/rpmmd2solv.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man1/mergesolv.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man1/repomdxml2solv.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man1/deltainfoxml2solv.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man1/rpms2solv.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man1/testsolv.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man1/updateinfoxml2solv.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man1/installcheck.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man3/libsolv-constantids.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man3/libsolv.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man3/libsolv-bindings.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man3/libsolv-history.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libsolv: /libsolv-doc/usr/share/man/man3/libsolv-pool.3 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_package_qa: Succeeded
NOTE: recipe libsolv-0.6.33-r0: task do_package_write_ipk: Succeeded
NOTE: recipe dsm-config-update-git-r2: task do_package: Succeeded
NOTE: recipe linux-5.1.7-5.1.7-r0: task do_unpack: Succeeded
NOTE: recipe libupnp-1.6.19-r2: task do_configure: Succeeded
NOTE: Tasks Summary: Attempted 3965 tasks of which 3952 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 6 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 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
Not sending mail to unregistered user andreas.fenkart at dev.digitalstrom.org