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

[dS Jenkins]

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

Changes:

[andreas.fenkart] reflash_rootfs: TODO: extract_release_type fails to zero-parse

[andreas.fenkart] oecore: udev: mtd-partition rules for pre 5.x kernels

[andreas.fenkart] rescue: swuimage-checks: update rootfs_part in u-boot env

[Krzysztof.Michonski] rescue-usbimage: dssip: adapt kernel naming to linux-5.0

[Krzysztof.Michonski] rescue: swupdate: remove local values from global space

[Krzysztof.Michonski] rescue: swupdate: unescaped '\' in libconfig object

[Krzysztof.Michonski] rootfs: udev: add a colon for consistency

[Krzysztof.Michonski] rootfs: udev: create link to rw device, not ro

------------------------------------------
[...truncated 317.04 KB...]
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/button_m/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/dss/coupler/joker/button_m/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/dss/coupler/joker/button_m/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/dss/coupler/joker/button_m/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/dss/coupler/joker/button_m/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/dss/coupler/joker/button_m/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/dss/coupler/joker/button_m/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/dss/coupler/joker/button_m/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/dss/coupler/joker/button_m/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/dss/coupler/joker/coupler_l/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/dss/coupler/joker/coupler_l/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/dss/coupler/joker/coupler_l/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/dss/coupler/joker/coupler_l/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/dss/coupler/joker/coupler_l/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/dss/coupler/joker/coupler_l/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/dss/coupler/joker/coupler_l/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/dss/coupler/joker/coupler_l/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/dss/coupler/joker/coupler_l/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/dss/coupler/joker/adapter/rot.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/dss/coupler/joker/adapter/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/dss/coupler/joker/adapter/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/dss/coupler/joker/adapter/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/dss/coupler/joker/adapter/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/dss/coupler/joker/adapter/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/dss/coupler/joker/adapter/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/dss/coupler/joker/adapter/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/dss/coupler/joker/adapter/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/dss/coupler/joker/coupler_m/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/dss/coupler/joker/coupler_m/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/dss/coupler/joker/coupler_m/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/dss/coupler/joker/coupler_m/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/dss/coupler/joker/coupler_m/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/dss/coupler/joker/coupler_m/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/dss/coupler/joker/coupler_m/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/dss/coupler/joker/coupler_m/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/dss/coupler/joker/coupler_m/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/kl/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/kl/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/kl/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/kl/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/kl/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/kl/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/kl/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/kl/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/kl/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/kl/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/kl/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/kl/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/kl/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/kl/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/kl/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/kl/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/kl/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/kl/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/akm/sensor.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/default/star_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/default/star_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/default/star_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/default/star_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/default/star_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/default/star_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/default/star_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/default/star_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/default/star_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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/tkm/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/sds/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/sds/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/sds/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/sds/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/sds/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/sds/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/sds/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/sds/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/sds/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/sds/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/sds/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/sds/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/sds/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/sds/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/sds/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/sds/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/sds/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/sds/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/zws/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/zws/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/zws/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/zws/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/zws/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/zws/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/zws/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/zws/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/zws/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/zws/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/zws/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/zws/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/zws/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/zws/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/zws/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/zws/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/zws/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/zws/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/sdm/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/sdm/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/sdm/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/sdm/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/sdm/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/sdm/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/sdm/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/sdm/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/sdm/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/sdm/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/sdm/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/sdm/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/sdm/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/sdm/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/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 rescue-install-git-r2: task do_install: Started
NOTE: recipe libupnp-1.6.19-r2: task do_package_qa: 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.31491)
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.31491
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-bsp/u-boot/u-boot-mkimage_2018.01.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-runtime_7.3.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-devtools/pseudo/pseudo_git.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: ['pseudo-native']
| NOTE: Skipping as already exists in sysroot: ['u-boot-mkimage-native', 'glibc', 'gcc-runtime', 'gcc-cross-arm', 'quilt-native', 'openssl-native', 'libmpc-native', 'libtool-native', 'mpfr-native', 'gnu-config-native', 'binutils-cross-arm', 'texinfo-dummy-native', 'autoconf-native', 'automake-native', 'flex-native', 'gmp-native', 'zlib-native', 'linux-libc-headers', 'xz-native', 'libgcc', 'pkgconfig-native', 'bison-native', 'm4-native', 'gettext-minimal-native', 'coreutils-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.31491: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.31491)
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 3878 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_package_write_ipk)
NOTE: recipe systembackup-git-r1: task do_package: Succeeded
NOTE: recipe addon-framework-git-r2: task do_package_qa: Succeeded
WARNING: libupnp-1.6.19-r2 do_package_qa: QA Issue: libupnp: /libupnp/usr/lib/libthreadutil.so.6.0.4 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp/usr/lib/libupnp.so.6.3.3 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp/usr/lib/libixml.so.2.0.8 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: recipe libupnp-1.6.19-r2: task do_package_write_ipk: Started
WARNING: libupnp-1.6.19-r2 do_package_qa: QA Issue: libupnp: /libupnp-dev/usr/lib/pkgconfig/libupnp.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 libupnp-1.6.19-r2: task do_package_qa: Succeeded
NOTE: recipe libupnp-1.6.19-r2: task do_package_write_ipk: Succeeded
NOTE: recipe addon-framework-git-r2: task do_package_write_ipk: Succeeded
NOTE: recipe libpagekite-git-r4: task do_package: Succeeded
NOTE: recipe linux-5.1.7-5.1.7-r0: task do_unpack: Succeeded
NOTE: recipe busybox-1.27.2-r0: task do_compile: Succeeded
NOTE: Tasks Summary: Attempted 3878 tasks of which 3807 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 9 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