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

[dS Jenkins]

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

Changes:

[Krzysztof.Michonski] rescue: remove broken kexec workaround

------------------------------------------
[...truncated 70.05 KB...]
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-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]
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]
NOTE: recipe heating-controller-logger-git-r11: task do_install: Succeeded
NOTE: Running task 4339 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/heating-controller-logger_git.bb:do_package)
NOTE: recipe libsolv-0.6.33-r0: task do_package_qa: Succeeded
NOTE: Running task 4340 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/heating-controller-logger_git.bb:do_populate_sysroot)
NOTE: recipe heating-controller-logger-git-r11: task do_package: Started
NOTE: recipe heating-controller-logger-git-r11: task do_populate_sysroot: Started
NOTE: recipe libpagekite-git-r4: task do_install: Succeeded
NOTE: Running task 4341 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libpagekite/libpagekite_git.bb:do_package)
NOTE: recipe libpagekite-git-r4: task do_package: Started
NOTE: recipe rescue-install-git-r2: task do_fetch: Succeeded
NOTE: Running task 4342 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libpagekite/libpagekite_git.bb:do_populate_sysroot)
NOTE: recipe libpagekite-git-r4: task do_populate_sysroot: Started
NOTE: recipe nftables-0.7-r0: task do_compile: Succeeded
NOTE: Running task 4343 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/device-energy-collector_git.bb:do_populate_sysroot)
NOTE: recipe device-energy-collector-git-r8: task do_populate_sysroot: Started
NOTE: recipe libupnp-1.6.19-r2: task do_compile: Succeeded
NOTE: Running task 4344 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_install)
NOTE: recipe libupnp-1.6.19-r2: task do_install: Started
NOTE: recipe libsolv-0.6.33-r0: task do_package_write_ipk: Succeeded
NOTE: Running task 4345 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-extended/libsolv/libsolv_0.6.33.bb:do_rm_work)
NOTE: recipe libsolv-0.6.33-r0: task do_rm_work: Started
NOTE: recipe libupnp-1.6.19-r2: task do_install: Succeeded
NOTE: Running task 4346 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_package)
NOTE: recipe libsolv-0.6.33-r0: task do_rm_work: Succeeded
NOTE: recipe libupnp-1.6.19-r2: task do_package: Started
NOTE: Running noexec task 4347 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-extended/libsolv/libsolv_0.6.33.bb:do_rm_work_all)
NOTE: Running noexec task 4348 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-extended/libsolv/libsolv_0.6.33.bb:do_build)
NOTE: Running task 4349 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_populate_sysroot)
NOTE: recipe libupnp-1.6.19-r2: task do_populate_sysroot: Started
NOTE: recipe heating-controller-logger-git-r11: task do_populate_sysroot: Succeeded
NOTE: recipe device-energy-collector-git-r8: task do_populate_sysroot: Succeeded
NOTE: Running task 4350 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-filter/nftables/nftables_0.7.bb:do_install)
NOTE: Running task 4351 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_prepare_recipe_sysroot)
NOTE: recipe rescue-install-git-r2: task do_prepare_recipe_sysroot: Started
NOTE: recipe nftables-0.7-r0: task do_install: Started
NOTE: recipe libpagekite-git-r4: task do_populate_sysroot: Succeeded
NOTE: Running task 4352 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_unpack)
NOTE: recipe rescue-install-git-r2: task do_unpack: Started
NOTE: recipe rescue-install-git-r2: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 4353 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-virtual-devices/doorbird/vdc-ui-doorbird_git.bb:do_unpack)
NOTE: recipe vdc-ui-doorbird-git-r2: task do_unpack: Started
NOTE: recipe rescue-install-git-r2: task do_unpack: Succeeded
NOTE: Running task 4354 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_patch)
NOTE: recipe nftables-0.7-r0: task do_install: Succeeded
NOTE: Running task 4355 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-filter/nftables/nftables_0.7.bb:do_package)
NOTE: recipe rescue-install-git-r2: task do_patch: Started
NOTE: recipe rescue-install-git-r2: task do_patch: Succeeded
NOTE: recipe device-energy-collector-git-r8: task do_package: Succeeded
NOTE: Running task 4356 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_populate_lic)
NOTE: Running task 4357 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/device-energy-collector_git.bb:do_packagedata)
NOTE: recipe heating-controller-logger-git-r11: task do_package: Succeeded
NOTE: recipe nftables-0.7-r0: task do_package: Started
NOTE: Running task 4358 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/heating-controller-logger_git.bb:do_packagedata)
NOTE: recipe rescue-install-git-r2: task do_populate_lic: Started
NOTE: recipe device-energy-collector-git-r8: task do_packagedata: Started
NOTE: recipe heating-controller-logger-git-r11: task do_packagedata: Started
NOTE: recipe rescue-install-git-r2: task do_populate_lic: Succeeded
NOTE: Running task 4359 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-filter/nftables/nftables_0.7.bb:do_populate_sysroot)
NOTE: recipe nftables-0.7-r0: task do_populate_sysroot: Started
NOTE: recipe device-energy-collector-git-r8: task do_packagedata: Succeeded
NOTE: Running task 4360 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/device-energy-collector_git.bb:do_package_qa)
NOTE: recipe libpagekite-git-r4: task do_package: Succeeded
NOTE: Running task 4361 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/device-energy-collector_git.bb:do_package_write_ipk)
NOTE: recipe device-energy-collector-git-r8: task do_package_qa: Started
NOTE: recipe heating-controller-logger-git-r11: task do_packagedata: Succeeded
NOTE: Running task 4362 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/heating-controller-logger_git.bb:do_package_qa)
NOTE: recipe device-energy-collector-git-r8: task do_package_write_ipk: Started
NOTE: recipe heating-controller-logger-git-r11: task do_package_qa: Started
NOTE: recipe device-energy-collector-git-r8: task do_package_qa: Succeeded
NOTE: Running task 4363 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/heating-controller-logger_git.bb:do_package_write_ipk)
NOTE: recipe libupnp-1.6.19-r2: task do_populate_sysroot: Succeeded
NOTE: Running task 4364 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libpagekite/libpagekite_git.bb:do_packagedata)
NOTE: recipe heating-controller-logger-git-r11: task do_package_write_ipk: Started
NOTE: recipe libpagekite-git-r4: task do_packagedata: Started
NOTE: recipe heating-controller-logger-git-r11: task do_package_qa: Succeeded
NOTE: Running task 4365 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-core/tasks/task-statistic-tools.bb:do_package)
NOTE: recipe vdc-ui-doorbird-git-r2: task do_unpack: Succeeded
NOTE: Running task 4366 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_configure)
NOTE: recipe rescue-install-git-r2: task do_configure: Started
NOTE: recipe task-statistic-tools-1.0-r2: task do_package: Started
NOTE: recipe device-energy-collector-git-r8: task do_package_write_ipk: Succeeded
NOTE: Running task 4367 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/device-energy-collector_git.bb:do_rm_work)
NOTE: recipe rescue-install-git-r2: task do_configure: Succeeded
NOTE: Running task 4368 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_compile)
NOTE: recipe device-energy-collector-git-r8: task do_rm_work: Started
NOTE: recipe rescue-install-git-r2: task do_compile: Started
NOTE: recipe libpagekite-git-r4: task do_packagedata: Succeeded
NOTE: Running task 4369 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libpagekite/libpagekite_git.bb:do_package_qa)
NOTE: recipe rescue-install-git-r2: task do_compile: Succeeded
NOTE: Running task 4370 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libpagekite/libpagekite_git.bb:do_package_write_ipk)
NOTE: recipe libpagekite-git-r4: task do_package_qa: Started
NOTE: recipe libpagekite-git-r4: task do_package_write_ipk: Started
NOTE: recipe heating-controller-logger-git-r11: task do_package_write_ipk: Succeeded
NOTE: Running task 4371 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/heating-controller-logger_git.bb:do_rm_work)
NOTE: recipe device-energy-collector-git-r8: task do_rm_work: Succeeded
NOTE: Running noexec task 4372 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/device-energy-collector_git.bb:do_rm_work_all)
NOTE: Running noexec task 4373 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/device-energy-collector_git.bb:do_build)
NOTE: Running task 4374 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_check_image_size)
NOTE: recipe heating-controller-logger-git-r11: task do_rm_work: Started
NOTE: recipe rescue-install-git-r2: task do_check_image_size: Started
NOTE: recipe rescue-install-git-r2: task do_check_image_size: Succeeded
NOTE: Running task 4375 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install)
NOTE: recipe rescue-install-git-r2: task do_install: Started
NOTE: recipe libupnp-1.6.19-r2: task do_package: Succeeded
NOTE: Running task 4376 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_packagedata)
NOTE: recipe libpagekite-git-r4: task do_package_qa: Succeeded
NOTE: Running task 4377 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-virtual-devices/doorbird/vdc-ui-doorbird_git.bb:do_patch)
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.28762)
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.28762
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['virtual:native:/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-core/glibc/glibc_2.27.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/gcc/gcc-cross_7.3.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-devtools/gcc/gcc-runtime_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']
| NOTE: Installed into sysroot: ['pseudo-native']
| NOTE: Skipping as already exists in sysroot: ['glibc', 'gcc-cross-arm', 'quilt-native', 'gcc-runtime', 'u-boot-mkimage-native', 'libtool-native', 'gnu-config-native', 'libmpc-native', 'xz-native', 'texinfo-dummy-native', 'binutils-cross-arm', 'zlib-native', 'mpfr-native', 'flex-native', 'linux-libc-headers', 'autoconf-native', 'automake-native', 'gmp-native', 'libgcc', 'openssl-native', 'gettext-minimal-native', 'bison-native', 'm4-native', 'coreutils-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.28762: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.28762)
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 vdc-ui-doorbird-git-r2: task do_patch: Started
NOTE: recipe vdc-ui-doorbird-git-r2: task do_patch: Succeeded
NOTE: recipe libupnp-1.6.19-r2: task do_packagedata: Started
NOTE: recipe heating-controller-logger-git-r11: task do_rm_work: Succeeded
NOTE: recipe libpagekite-git-r4: task do_package_write_ipk: Succeeded
NOTE: recipe libupnp-1.6.19-r2: task do_packagedata: Succeeded
NOTE: recipe nftables-0.7-r0: task do_populate_sysroot: Succeeded
NOTE: recipe nftables-0.7-r0: task do_package: Succeeded
NOTE: recipe task-statistic-tools-1.0-r2: task do_package: Succeeded
NOTE: Tasks Summary: Attempted 4378 tasks of which 4299 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 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