[dss-merge-requests] Build failed in Jenkins: yocto #3195
dS Jenkins
jenkins at dev.digitalstrom.org
Thu Aug 22 12:34:48 CEST 2019
See <http://dsjenkins.cloudapp.net/jenkins/job/yocto/3195/display/redirect?page=changes>
Changes:
[jin] Synced production with fieldtest for R1908 / 1.16.2
------------------------------------------
[...truncated 27.79 KB...]
NOTE: recipe update-info-file-0.1-r1: task do_prepare_recipe_sysroot: Started
NOTE: recipe rescue-usbimage-1.0-r2: task do_fetch: Succeeded
NOTE: Running task 2539 of 2564 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usbimage.bb:do_prepare_recipe_sysroot)
NOTE: Running task 2540 of 2564 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usbimage.bb:do_unpack)
NOTE: recipe rescue-usbimage-1.0-r2: task do_prepare_recipe_sysroot: Started
NOTE: recipe rescue-usbimage-1.0-r2: task do_unpack: Started
NOTE: recipe rescue-usbimage-1.0-r2: task do_unpack: Succeeded
NOTE: recipe update-info-file-0.1-r1: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running noexec task 2543 of 2564 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_configure)
NOTE: Running task 2544 of 2564 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_compile)
NOTE: recipe rescue-usbimage-1.0-r2: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 2545 of 2564 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usbimage.bb:do_usbimage)
NOTE: recipe update-info-file-0.1-r1: task do_compile: Started
NOTE: recipe update-info-file-0.1-r1: task do_compile: Succeeded
NOTE: Running task 2552 of 2564 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_deploy)
NOTE: recipe rescue-usbimage-1.0-r2: task do_usbimage: Started
NOTE: recipe update-info-file-0.1-r1: task do_deploy: Started
NOTE: recipe update-info-file-0.1-r1: task do_deploy: Succeeded
NOTE: Running task 2559 of 2564 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_rm_work)
NOTE: recipe update-info-file-0.1-r1: task do_rm_work: Started
NOTE: recipe update-info-file-0.1-r1: task do_rm_work: Succeeded
NOTE: Running noexec task 2560 of 2564 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_rm_work_all)
NOTE: Running noexec task 2561 of 2564 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_build)
NOTE: recipe rescue-usbimage-1.0-r2: task do_usbimage: Succeeded
NOTE: Running task 2562 of 2564 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usbimage.bb:do_rm_work)
NOTE: recipe rescue-usbimage-1.0-r2: task do_rm_work: Started
NOTE: recipe rescue-usbimage-1.0-r2: task do_rm_work: Succeeded
NOTE: Running noexec task 2563 of 2564 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usbimage.bb:do_rm_work_all)
NOTE: Running noexec task 2564 of 2564 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usbimage.bb:do_build)
NOTE: Tasks Summary: Attempted 2564 tasks of which 2547 didn't need to be rerun and all succeeded.
NOTE: No commit since BUILDHISTORY_COMMIT != '1'
NOTE: Syncing deploy/images.
[INFO] building package-index
NOTE: Started PRServer with DBfile: /home/****/workspace/yocto/poky-rescue-devel-build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 44049, PID: 623
Loading cache...done.
Loaded 2912 entries from dependency cache.
Parsing recipes...done.
Parsing of 2051 .bb files complete (2047 cached, 4 parsed). 2916 targets, 339 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.38.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal-4.8"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "dss20"
DISTRO = "poky"
DISTRO_VERSION = "2.5.2"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "HEAD:623b77885051174d0e05198843e739110977bd18"
meta-oe
meta-python
meta-networking
meta-webserver = "HEAD:8760facba1bceb299b3613b8955621ddaa3d4c3f"
meta-swupdate = "HEAD:f2d65d87485ada5a2d3a744fd7b9e46ec7e6b9f2"
meta-digitalstrom-rescue-devel = "HEAD:0d555efe924e064226072e0556a217c94babef3d"
Initialising tasks...done.
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running noexec task 322 of 326 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-core/meta/package-index.bb:do_rm_work_all)
NOTE: Running task 323 of 326 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-core/meta/package-index.bb:do_package_index)
NOTE: recipe package-index-1.0-r0: task do_package_index: Started
NOTE: recipe package-index-1.0-r0: task do_package_index: Succeeded
NOTE: Running task 325 of 326 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-core/meta/package-index.bb:do_rm_work)
NOTE: recipe package-index-1.0-r0: task do_rm_work: Started
NOTE: recipe package-index-1.0-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 326 of 326 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-core/meta/package-index.bb:do_build)
NOTE: Tasks Summary: Attempted 326 tasks of which 322 didn't need to be rerun and all succeeded.
NOTE: No commit since BUILDHISTORY_COMMIT != '1'
NOTE: Syncing deploy/images.
Configured feed: "devel"
Building configuration for targets/devel/dss20-yocto
[INFO] PACKAGES: update-info-file
NOTE: Started PRServer with DBfile: /home/****/workspace/yocto/poky-devel-nopkg-build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 35451, PID: 929
Loading cache...done.
Loaded 3193 entries from dependency cache.
Parsing recipes...done.
Parsing of 2397 .bb files complete (2288 cached, 109 parsed). 3307 targets, 433 skipped, 46 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.38.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal-4.8"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "dss20"
DISTRO = "poky"
DISTRO_VERSION = "2.5.2"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "HEAD:623b77885051174d0e05198843e739110977bd18"
meta-oe
meta-python
meta-networking
meta-webserver
meta-multimedia = "HEAD:8760facba1bceb299b3613b8955621ddaa3d4c3f"
meta-freescale = "HEAD:407c6cf408969445031a492e2d25e0e2749582ea"
meta-swupdate = "HEAD:f2d65d87485ada5a2d3a744fd7b9e46ec7e6b9f2"
meta-digitalstrom-devel = "HEAD:0d555efe924e064226072e0556a217c94babef3d"
Initialising tasks...done.
NOTE: Executing SetScene Tasks
NOTE: Running setscene task 2004 of 2240 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/device-energy-collector_git.bb:do_package_write_ipk_setscene)
NOTE: recipe device-energy-collector-git-r8: task do_package_write_ipk_setscene: Started
NOTE: recipe device-energy-collector-git-r8: task do_package_write_ipk_setscene: Succeeded
NOTE: Executing RunQueue Tasks
NOTE: Running task 3141 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel-extra-layers/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb:do_install)
ERROR: When reparsing /home/****/workspace/yocto/yocto/feedconfig/devel-extra-layers/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb.do_configure, the basehash value changed from b13d8329043b7e716082ee5a3a1014be to a0be549f0ad03beb494746734de76a81. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /home/****/workspace/yocto/yocto/feedconfig/devel-extra-layers/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb.do_package, the basehash value changed from 4ed6ee4cbef7df21393de34278086813 to bb8c186c6ddbcf02575b87490a97b5ad. The metadata is not deterministic and this needs to be fixed.
NOTE: recipe swupdate-2018.03-r0: task do_install: Started
NOTE: recipe swupdate-2018.03-r0: task do_install: Succeeded
NOTE: Running task 3800 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel-extra-layers/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb:do_populate_sysroot)
NOTE: Running task 3801 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel-extra-layers/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb:do_package)
ERROR: When reparsing /home/****/workspace/yocto/yocto/feedconfig/devel-extra-layers/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb.do_configure, the basehash value changed from b13d8329043b7e716082ee5a3a1014be to a0be549f0ad03beb494746734de76a81. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /home/****/workspace/yocto/yocto/feedconfig/devel-extra-layers/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb.do_package, the basehash value changed from 4ed6ee4cbef7df21393de34278086813 to bb8c186c6ddbcf02575b87490a97b5ad. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /home/****/workspace/yocto/yocto/feedconfig/devel-extra-layers/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb.do_configure, the basehash value changed from b13d8329043b7e716082ee5a3a1014be to a0be549f0ad03beb494746734de76a81. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing /home/****/workspace/yocto/yocto/feedconfig/devel-extra-layers/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb.do_package, the basehash value changed from 4ed6ee4cbef7df21393de34278086813 to bb8c186c6ddbcf02575b87490a97b5ad. The metadata is not deterministic and this needs to be fixed.
NOTE: recipe swupdate-2018.03-r0: task do_populate_sysroot: Started
NOTE: Running task 4013 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install)
NOTE: recipe swupdate-2018.03-r0: task do_package: Started
NOTE: Running task 4057 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-filter/nftables/nftables_0.7.bb:do_package_qa)
NOTE: Running task 4058 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-filter/nftables/nftables_0.7.bb:do_package_write_ipk)
NOTE: Running noexec task 4073 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 4074 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/device-energy-collector_git.bb:do_build)
NOTE: Running task 4117 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/heating-controller-logger_git.bb:do_packagedata)
NOTE: Running task 4135 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-addons/led-wizard/led-wizard_git.bb:do_prepare_recipe_sysroot)
NOTE: Running task 4136 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-addons/led-wizard/led-wizard_git.bb:do_unpack)
NOTE: recipe rescue-install-git-r2: task do_install: Started
NOTE: recipe nftables-0.7-r0: task do_package_write_ipk: Started
NOTE: recipe led-wizard-git-r1: task do_prepare_recipe_sysroot: Started
NOTE: recipe led-wizard-git-r1: task do_unpack: Started
NOTE: recipe led-wizard-git-r1: task do_prepare_recipe_sysroot: Succeeded
NOTE: recipe heating-controller-logger-git-r11: task do_packagedata: Started
NOTE: recipe nftables-0.7-r0: 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.2244)
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.2244
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-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-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/gcc/gcc-runtime_7.3.bb:do_populate_sysroot', 'virtual:native:/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['gcc-cross-arm', 'quilt-native', 'glibc', 'u-boot-mkimage-native', 'gcc-runtime', 'pseudo-native', 'linux-libc-headers', 'openssl-native', 'autoconf-native', 'libtool-native', 'xz-native', 'binutils-cross-arm', 'flex-native', 'gnu-config-native', 'gmp-native', 'zlib-native', 'mpfr-native', 'libmpc-native', 'texinfo-dummy-native', 'automake-native', 'libgcc', 'pkgconfig-native', 'm4-native', 'gettext-minimal-native', 'bison-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.2244: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.2244)
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 swupdate-2018.03-r0: task do_populate_sysroot: Succeeded
NOTE: recipe led-wizard-git-r1: task do_unpack: Succeeded
WARNING: nftables-0.7-r0 do_package_qa: QA Issue: nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/datatype.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/rbtree.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/evaluate.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/numgen.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/gmputil.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/netlink.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/erec.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/netlink_delinearize.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/cli.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/fib.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/payload.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/parser_bison.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/ct.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/rt.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/statement.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/expression.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/iface.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/mnl.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/hash.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/meta.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/exthdr.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/rule.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/proto.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/utils.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/netlink_linearize.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/services.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/segtree.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/src/main.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/payload.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/ct.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/utils.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/expression.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/iface.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/rt.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/gmputil.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/rule.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/proto.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/rbtree.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/xt.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/headers.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/hash.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/erec.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/meta.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/netlink.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/nftables.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/cli.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/datatype.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/statement.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/numgen.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/mnl.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/list.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/exthdr.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/parser.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/fib.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/linux/netfilter.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/linux/netfilter/nf_tables.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/linux/netfilter/nf_conntrack_common.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/linux/netfilter/nf_conntrack_tuple_common.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/src/debug/nftables/0.7-r0/nftables-0.7/include/linux/netfilter/nfnetlink.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables-dbg/usr/sbin/.debug/nft 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: nftables-0.7-r0 do_package_qa: QA Issue: nftables: /nftables/usr/sbin/nft is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables/etc/nftables/inet-filter is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables/etc/nftables/ipv4-nat is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables/etc/nftables/ipv6-nat is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables/etc/nftables/ipv6-mangle is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables/etc/nftables/ipv4-mangle is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables/etc/nftables/bridge-filter is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables/etc/nftables/ipv6-filter is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
nftables: /nftables/etc/nftables/ipv4-filter 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_packagedata: Succeeded
NOTE: recipe nftables-0.7-r0: task do_package_qa: Succeeded
NOTE: recipe nftables-0.7-r0: task do_package_write_ipk: Succeeded
ERROR: swupdate-2018.03-r0 do_package: Taskhash mismatch b699ede16c962eefacbdc1f00f295ff9 versus b3e6a9d6e44809c890eb506173690e85 for /home/****/workspace/yocto/yocto/feedconfig/devel-extra-layers/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb.do_package
NOTE: recipe swupdate-2018.03-r0: task do_package: Succeeded
ERROR: Taskhash mismatch b699ede16c962eefacbdc1f00f295ff9 versus b3e6a9d6e44809c890eb506173690e85 for /home/****/workspace/yocto/yocto/feedconfig/devel-extra-layers/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb.do_package
NOTE: Tasks Summary: Attempted 4334 tasks of which 4323 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 2 WARNING messages shown.
Summary: There were 9 ERROR messages 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 jean.visagie at digitalstrom.com
Not sending mail to unregistered user Krzysztof.Michonski at digitalstrom.com
Not sending mail to unregistered user andreas.fenkart at dev.digitalstrom.org
More information about the dSS-merge-requests
mailing list