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

[dS Jenkins]

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

Changes:

[Krzysztof.Michonski] rootfs: rescue-utils: create empty executable common-paths.env

[andreas.fenkart] rescue: enable append_devel overrides

[andreas.fenkart] recue: site.conf: DIGITALSTROM_GIT_BRANCH set in setup-yocto.sh

[andreas.fenkart] rescue-system: enable swupdate http fetcher on devel feed

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

------------------------------------------
[...truncated 402.80 KB...]
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/black_grey.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/grey.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/red.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/yellow.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_white.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/white.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_yellow.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/blue.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_magenta.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/cyan.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/magenta.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_cyan.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_red.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_blue.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_green.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_black.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/green.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_grey.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/grey.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/red.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_fire.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_absent.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_sun_protection.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_alarm1.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_blink.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_25.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_sun_protection.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_alarm2.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_alarm3.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_deep_off.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_norain.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_alarm4.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_75.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_alarm4.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_stop.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_wakeup.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_on.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_present.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_rain.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_33.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_alarm2.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_alarm3.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_panic.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_66.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_50.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_fire.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_bell.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_off.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_panic.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_sleeping.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_alarm1.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_standby.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/css/dss-responsive-ui.css is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/dss-responsive-ui.js is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/vendor/polyfill.min.js is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/vendor/jquery.min.js is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/vendor/modernizr.custom.js is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/vendor/foundation.min.js is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/vendor/motion-ui/motion-ui.min.js is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/vendor/motion-ui/motion-ui.min.css is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/images/ds_logo.png is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/fontawesome-webfont.woff2 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/fontawesome-webfont.woff is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/DINNext-Regular.woff is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/fontawesome-webfont.ttf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/DINWeb.woff is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/fontawesome-webfont.svg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/DINWeb-Medium.woff is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/FontAwesome.otf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/fontawesome-webfont.eot 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 ntp-4.2.8p11-r0: task do_package_write_ipk: Started
WARNING: ntp-4.2.8p11-r0 do_package_qa: QA Issue: ntp: /ntp-utils/usr/share/ntp/lib/NTP/Util.pm is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/calc_tickadj is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/ntpdc is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/ntp-wait is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/ntptrace is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/ntptime is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/ntpq is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/ntp-keygen 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 addon-framework-git-r2: task do_package_qa: Succeeded
NOTE: Running task 3959 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-fw-upgrade/dsm-firmware_git.bb:do_packagedata)
NOTE: recipe dsm-firmware-git-r1: task do_packagedata: Started
WARNING: ntp-4.2.8p11-r0 do_package_qa: QA Issue: ntp: /ntp/usr/sbin/ntpd.ntp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp/etc/ntp.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp/etc/init.d/ntpd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp/etc/default/ntpclient 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 rrdtool-1.6.0-r0: task do_package: Succeeded
NOTE: Running task 3960 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-oe/recipes-extended/rrdtool/rrdtool_1.6.0.bb:do_packagedata)
NOTE: recipe rrdtool-1.6.0-r0: task do_packagedata: Started
NOTE: recipe dsm-firmware-git-r1: task do_packagedata: Succeeded
NOTE: Running task 3961 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-fw-upgrade/dsm-firmware_git.bb:do_package_qa)
NOTE: recipe ntp-4.2.8p11-r0: task do_package_qa: Succeeded
NOTE: Running task 3962 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dss11-websetup/dss11-websetup_git.bb:do_package_qa)
NOTE: recipe dsm-firmware-git-r1: task do_package_qa: Started
NOTE: recipe dss11-websetup-git-r1: task do_package_qa: Started
NOTE: recipe rrdtool-1.6.0-r0: task do_packagedata: Succeeded
NOTE: Running task 3963 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-oe/recipes-extended/rrdtool/rrdtool_1.6.0.bb:do_package_qa)
NOTE: recipe dsm-firmware-git-r1: task do_package_qa: Succeeded
NOTE: Running task 3964 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-fw-upgrade/dsm-firmware_git.bb:do_package_write_ipk)
NOTE: recipe dsm-firmware-git-r1: task do_package_write_ipk: Started
NOTE: recipe rrdtool-1.6.0-r0: task do_package_qa: Started
NOTE: recipe addon-framework-git-r2: task do_package_write_ipk: Succeeded
NOTE: Running task 3965 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-system-addons/framework/addon-framework_git.bb:do_rm_work)
NOTE: recipe rrdtool-1.6.0-r0: task do_package_qa: Succeeded
NOTE: Running task 3966 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dss11-websetup/dss11-websetup_git.bb:do_package_write_ipk)
NOTE: recipe addon-framework-git-r2: task do_rm_work: Started
NOTE: recipe dsm-firmware-git-r1: task do_package_write_ipk: Succeeded
NOTE: Running task 3967 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-oe/recipes-extended/rrdtool/rrdtool_1.6.0.bb:do_package_write_ipk)
NOTE: recipe dss11-websetup-git-r1: task do_package_write_ipk: Started
NOTE: recipe rrdtool-1.6.0-r0: task do_package_write_ipk: Started
NOTE: recipe dss11-websetup-git-r1: task do_package_qa: Succeeded
NOTE: Running task 3968 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-devtools/xmlrpc-c/xmlrpc-c_1.39.12.bb:do_populate_sysroot)
NOTE: recipe addon-framework-git-r2: task do_rm_work: Succeeded
NOTE: Running noexec task 3969 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-system-addons/framework/addon-framework_git.bb:do_rm_work_all)
NOTE: Running noexec task 3970 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-system-addons/framework/addon-framework_git.bb:do_build)
NOTE: Running task 3971 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-fw-upgrade/dsm-firmware_git.bb:do_populate_sysroot)
NOTE: recipe dsm-firmware-git-r1: task do_populate_sysroot: Started
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_populate_sysroot: Started
NOTE: recipe dsm-firmware-git-r1: task do_populate_sysroot: Succeeded
NOTE: Running task 3972 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-fw-upgrade/dsm-firmware_git.bb:do_rm_work)
NOTE: recipe dsm-firmware-git-r1: task do_rm_work: Started
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_compile: Succeeded
NOTE: Running task 3973 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-kernel/lttng/lttng-ust_2.10.1.bb:do_install)
NOTE: recipe dsm-firmware-git-r1: task do_rm_work: Succeeded
NOTE: Running noexec task 3974 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-fw-upgrade/dsm-firmware_git.bb:do_rm_work_all)
NOTE: Running noexec task 3975 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-fw-upgrade/dsm-firmware_git.bb:do_build)
NOTE: Running task 3981 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/ds485p/ds485p_git.bb:do_configure)
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_install: Started
NOTE: recipe ds485p-git-r5: task do_configure: Started
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_populate_sysroot: Succeeded
NOTE: Running task 3982 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_fetch)
NOTE: recipe rescue-install-git-r2: task do_fetch: Started
NOTE: recipe rrdtool-1.6.0-r0: task do_package_write_ipk: Succeeded
NOTE: Running task 3983 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-oe/recipes-extended/rrdtool/rrdtool_1.6.0.bb:do_rm_work)
NOTE: recipe rrdtool-1.6.0-r0: task do_rm_work: Started
NOTE: recipe dss11-websetup-git-r1: task do_package_write_ipk: Succeeded
NOTE: Running task 3984 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dss11-websetup/dss11-websetup_git.bb:do_rm_work)
NOTE: recipe dss11-websetup-git-r1: task do_rm_work: Started
NOTE: recipe rrdtool-1.6.0-r0: task do_rm_work: Succeeded
NOTE: Running task 3986 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_prepare_recipe_sysroot)
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_install: Succeeded
NOTE: Running task 3987 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-kernel/lttng/lttng-ust_2.10.1.bb:do_package)
NOTE: recipe libupnp-1.6.19-r2: task do_prepare_recipe_sysroot: Started
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_package: Started
NOTE: recipe dss11-websetup-git-r1: task do_rm_work: Succeeded
NOTE: Running task 3988 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-kernel/lttng/lttng-ust_2.10.1.bb:do_populate_sysroot)
NOTE: recipe libupnp-1.6.19-r2: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 3992 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_configure)
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_populate_sysroot: Started
NOTE: recipe libupnp-1.6.19-r2: task do_configure: Started
NOTE: recipe strace-4.20-r0: task do_package_qa: Succeeded
NOTE: Running task 3993 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/strace/strace_4.20.bb:do_rm_work)
NOTE: recipe ntp-4.2.8p11-r0: task do_package_write_ipk: Succeeded
NOTE: Running task 3994 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-support/ntp/ntp_4.2.8p11.bb:do_rm_work)
NOTE: recipe strace-4.20-r0: task do_rm_work: Started
NOTE: recipe ntp-4.2.8p11-r0: task do_rm_work: Started
NOTE: recipe ntp-4.2.8p11-r0: task do_rm_work: Succeeded
NOTE: recipe strace-4.20-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 3995 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/strace/strace_4.20.bb:do_rm_work_all)
NOTE: Running noexec task 3996 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/strace/strace_4.20.bb:do_build)
NOTE: Running noexec task 3997 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-support/ntp/ntp_4.2.8p11.bb:do_rm_work_all)
NOTE: Running noexec task 3998 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-support/ntp/ntp_4.2.8p11.bb:do_build)
NOTE: Running noexec task 3999 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dss11-websetup/dss11-websetup_git.bb:do_rm_work_all)
NOTE: Running noexec task 4000 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dss11-websetup/dss11-websetup_git.bb:do_build)
NOTE: Running task 4002 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libpagekite/libpagekite_git.bb:do_prepare_recipe_sysroot)
NOTE: Running task 4007 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-filter/nftables/nftables_0.7.bb:do_prepare_recipe_sysroot)
NOTE: recipe libpagekite-git-r4: task do_prepare_recipe_sysroot: Started
NOTE: recipe nftables-0.7-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe rescue-install-git-r2: task do_fetch: Succeeded
NOTE: Running task 4008 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 libpagekite-git-r4: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 4009 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libpagekite/libpagekite_git.bb:do_configure)
NOTE: recipe nftables-0.7-r0: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 4010 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 xmlrpc-c-1.39.12-r2: task do_package: Succeeded
NOTE: Running task 4011 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-devtools/xmlrpc-c/xmlrpc-c_1.39.12.bb:do_packagedata)
NOTE: recipe libpagekite-git-r4: task do_configure: Started
NOTE: recipe rescue-install-git-r2: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 4015 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-filter/nftables/nftables_0.7.bb:do_configure)
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_packagedata: Started
NOTE: recipe nftables-0.7-r0: task do_configure: Started
NOTE: recipe rescue-install-git-r2: task do_unpack: Succeeded
NOTE: Running task 4016 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_patch)
NOTE: recipe rescue-install-git-r2: task do_patch: Started
NOTE: recipe rescue-install-git-r2: task do_patch: Succeeded
NOTE: Running task 4017 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_populate_lic)
NOTE: recipe rescue-install-git-r2: task do_populate_lic: Started
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_packagedata: Succeeded
NOTE: Running task 4018 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-devtools/xmlrpc-c/xmlrpc-c_1.39.12.bb:do_package_qa)
NOTE: recipe rescue-install-git-r2: task do_populate_lic: Succeeded
NOTE: Running task 4019 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-devtools/xmlrpc-c/xmlrpc-c_1.39.12.bb:do_package_write_ipk)
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_package_qa: Started
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_package_write_ipk: Started
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_populate_sysroot: Succeeded
NOTE: Running task 4020 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 rescue-install-git-r2: task do_configure: Succeeded
NOTE: Running task 4021 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_compile)
NOTE: recipe rescue-install-git-r2: task do_compile: Started
NOTE: recipe rescue-install-git-r2: task do_compile: Succeeded
NOTE: Running task 4022 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_check_image_size)
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 4023 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install)
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_package_qa: Succeeded
NOTE: Running task 4025 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/heating-controller-logger_git.bb:do_prepare_recipe_sysroot)
NOTE: recipe rescue-install-git-r2: task do_install: Started
NOTE: recipe heating-controller-logger-git-r11: task do_prepare_recipe_sysroot: Started
ERROR: rescue-install-git-r2 do_install: Function failed: do_install (log file is located at /home/****/workspace/yocto/poky-devel-nopkg-build/build/work/dss20-poky-linux-gnueabi/rescue-install/git-r2/temp/log.do_install.8134)
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.8134
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', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-core/glibc/glibc_2.27.bb:do_populate_sysroot', 'virtual:native:/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-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', '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']
| NOTE: Installed into sysroot: ['pseudo-native']
| NOTE: Skipping as already exists in sysroot: ['gcc-runtime', 'glibc', 'u-boot-mkimage-native', 'quilt-native', 'gcc-cross-arm', 'linux-libc-headers', 'libgcc', 'openssl-native', 'xz-native', 'flex-native', 'automake-native', 'zlib-native', 'gmp-native', 'autoconf-native', 'texinfo-dummy-native', 'binutils-cross-arm', 'mpfr-native', 'libtool-native', 'libmpc-native', 'gnu-config-native', 'pkgconfig-native', 'gettext-minimal-native', 'coreutils-native', 'm4-native', 'bison-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.8134: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.8134)
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 heating-controller-logger-git-r11: task do_prepare_recipe_sysroot: Succeeded
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_package: Succeeded
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_package_write_ipk: Succeeded
NOTE: recipe nftables-0.7-r0: task do_configure: Succeeded
NOTE: recipe libupnp-1.6.19-r2: task do_configure: Succeeded
NOTE: recipe ds485p-git-r5: task do_configure: Succeeded
NOTE: recipe libpagekite-git-r4: task do_configure: Succeeded
NOTE: Tasks Summary: Attempted 4026 tasks of which 3733 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 Krzysztof.Michonski at digitalstrom.com
Not sending mail to unregistered user andreas.fenkart at dev.digitalstrom.org
Not sending mail to unregistered user jin at developer.digitalstrom.org
Not sending mail to unregistered user jean.visagie at digitalstrom.com