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

Tue Jul 30 14:20:00 CEST 2019

See <http://dsjenkins.cloudapp.net/jenkins/job/yocto/3155/display/redirect>

------------------------------------------
[...truncated 68.00 KB...]
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/genlib/net/http/statcodes.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/genlib/net/http/parsetools.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/genlib/net/http/webserver.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/genlib/util/membuffer.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/genlib/util/util.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/genlib/util/upnp_timeout.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/genlib/util/strintmap.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/api/upnpapi.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/api/upnptools.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/api/UpnpString.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/urlconfig/urlconfig.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/sock.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/global.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/upnp_timeout.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/strintmap.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/parsetools.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/upnputil.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/httpparser.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/sysdep.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/upnpapi.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/md5.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/uuid.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/VirtualDir.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/urlconfig.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/gena_device.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/miniserver.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/statcodes.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/httpreadwrite.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/uri.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/ssdplib.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/service_table.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/gena_ctrlpt.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/membuffer.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/webserver.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/client_table.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/soaplib.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/inc/gena.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/soap/soap_common.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/soap/soap_ctrlpt.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/src/soap/soap_device.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/inc/UpnpString.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/inc/UpnpInet.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/inc/upnp.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/upnp/inc/upnpdebug.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/threadutil/src/ThreadPool.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/threadutil/src/TimerThread.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/threadutil/src/FreeList.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/threadutil/src/LinkedList.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/threadutil/inc/ThreadPool.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/threadutil/inc/FreeList.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/threadutil/inc/ithread.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/threadutil/inc/TimerThread.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/threadutil/inc/LinkedList.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/ixml/src/ixmlparser.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/ixml/src/element.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/ixml/src/ixml.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/ixml/src/namedNodeMap.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/ixml/src/document.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/ixml/src/nodeList.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/ixml/src/attr.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/ixml/src/ixmlmembuf.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/ixml/src/node.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/ixml/src/inc/ixmlmembuf.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/ixml/src/inc/ixmlparser.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/ixml/inc/ixmldebug.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/src/debug/libupnp/1.6.19-r2/libupnp-1.6.19/ixml/inc/ixml.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
libupnp: /libupnp-dbg/usr/lib/.debug/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-dbg/usr/lib/.debug/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-dbg/usr/lib/.debug/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: Running noexec task 4932 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-core/tasks/task-system-addons.bb:do_rm_work_all)
NOTE: Running noexec task 4933 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-core/tasks/task-system-addons.bb:do_build)
NOTE: Running noexec task 4951 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-addons/wesco/wesco-balance_1.0.0.bb:do_rm_work_all)
NOTE: Running noexec task 4952 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-addons/wesco/wesco-balance_1.0.0.bb:do_build)
NOTE: Running noexec task 4955 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-core/tasks/task-addons.bb:do_rm_work_all)
NOTE: Running noexec task 4956 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-core/tasks/task-addons.bb:do_build)
NOTE: Running task 4958 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-oe/recipes-benchmark/fio/fio_2.9.bb:do_prepare_recipe_sysroot)
NOTE: recipe vdc-ui-doorbird-git-r2: task do_populate_lic: Succeeded
NOTE: Running task 4963 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-connectivity/iproute2/iproute2_4.14.1.bb:do_prepare_recipe_sysroot)
NOTE: recipe nftables-0.7-r0: task do_packagedata: Succeeded
NOTE: Running task 4964 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-filter/nftables/nftables_0.7.bb:do_package_qa)
NOTE: recipe fio-2.9-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe iproute2-4.14.1-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe nftables-0.7-r0: task do_package_qa: Started
NOTE: recipe libupnp-1.6.19-r2: task do_package_qa: Succeeded
NOTE: Running task 4965 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: recipe iproute2-4.14.1-r0: task do_prepare_recipe_sysroot: Succeeded
NOTE: recipe nftables-0.7-r0: task do_package_write_ipk: Started
NOTE: Running task 4969 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-connectivity/iproute2/iproute2_4.14.1.bb:do_configure)
NOTE: recipe fio-2.9-r0: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 4970 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-oe/recipes-benchmark/fio/fio_2.9.bb:do_configure)
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 iproute2-4.14.1-r0: task do_configure: Started
NOTE: recipe fio-2.9-r0: task do_configure: Started
NOTE: recipe rescue-install-git-r2: task do_fetch: Succeeded
NOTE: Running task 4971 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_prepare_recipe_sysroot)
NOTE: recipe rescue-install-git-r2: task do_prepare_recipe_sysroot: Started
NOTE: recipe nftables-0.7-r0: task do_package_qa: Succeeded
NOTE: Running task 4972 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 libupnp-1.6.19-r2: task do_package_write_ipk: Succeeded
NOTE: Running task 4973 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_rm_work)
NOTE: recipe rescue-install-git-r2: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 4975 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-bsp/fsl-otp-tool/fsl-otp-tool_git.bb:do_prepare_recipe_sysroot)
NOTE: recipe libupnp-1.6.19-r2: task do_rm_work: Started
NOTE: recipe fsl-otp-tool-git-r1: task do_prepare_recipe_sysroot: Started
NOTE: recipe rescue-install-git-r2: task do_unpack: Succeeded
NOTE: Running task 4976 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: recipe libupnp-1.6.19-r2: task do_rm_work: Succeeded
NOTE: Running task 4977 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_populate_lic)
NOTE: Running noexec task 4978 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_rm_work_all)
NOTE: Running noexec task 4979 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_build)
NOTE: Running task 4980 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_configure)
NOTE: recipe fsl-otp-tool-git-r1: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 4984 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-bsp/fsl-otp-tool/fsl-otp-tool_git.bb:do_configure)
NOTE: recipe rescue-install-git-r2: task do_populate_lic: Started
NOTE: recipe rescue-install-git-r2: task do_configure: Started
NOTE: recipe fsl-otp-tool-git-r1: task do_configure: Started
NOTE: recipe nftables-0.7-r0: task do_package_write_ipk: Succeeded
NOTE: recipe rescue-install-git-r2: task do_configure: Succeeded
NOTE: Running task 4985 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-filter/nftables/nftables_0.7.bb:do_rm_work)
NOTE: Running task 4986 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_populate_lic: Succeeded
NOTE: recipe nftables-0.7-r0: task do_rm_work: Started
NOTE: Running task 4988 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-extended/minicom/minicom_2.7.1.bb:do_prepare_recipe_sysroot)
NOTE: recipe minicom-2.7.1-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe rescue-install-git-r2: task do_compile: Succeeded
NOTE: Running task 4989 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_check_image_size)
NOTE: recipe nftables-0.7-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 4990 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-filter/nftables/nftables_0.7.bb:do_rm_work_all)
NOTE: Running task 4995 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-devtools/inotify-tools/inotify-tools_3.14.bb:do_prepare_recipe_sysroot)
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 4996 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install)
NOTE: recipe inotify-tools-3.14-r2: task do_prepare_recipe_sysroot: Started
NOTE: recipe rescue-install-git-r2: task do_install: Started
NOTE: recipe minicom-2.7.1-r0: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 4997 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-extended/minicom/minicom_2.7.1.bb:do_configure)
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.24951)
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.24951
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/quilt/quilt-native_0.65.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/gcc/gcc-runtime_7.3.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: ['pseudo-native']
| NOTE: Skipping as already exists in sysroot: ['u-boot-mkimage-native', 'glibc', 'quilt-native', 'gcc-cross-arm', 'gcc-runtime', 'openssl-native', 'linux-libc-headers', 'mpfr-native', 'flex-native', 'gnu-config-native', 'xz-native', 'texinfo-dummy-native', 'zlib-native', 'libtool-native', 'gmp-native', 'autoconf-native', 'binutils-cross-arm', 'automake-native', 'libmpc-native', 'libgcc', '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.24951: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.24951)
NOTE: recipe rescue-install-git-r2: task do_install: Failed
NOTE: recipe inotify-tools-3.14-r2: task do_prepare_recipe_sysroot: Succeeded
NOTE: recipe minicom-2.7.1-r0: task do_configure: Started
NOTE: Running task 5001 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-devtools/inotify-tools/inotify-tools_3.14.bb:do_configure)
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 inotify-tools-3.14-r2: task do_configure: Started
NOTE: recipe iproute2-4.14.1-r0: task do_configure: Succeeded
NOTE: recipe fio-2.9-r0: task do_configure: Succeeded
NOTE: recipe fsl-otp-tool-git-r1: task do_configure: Succeeded
NOTE: recipe minicom-2.7.1-r0: task do_configure: Succeeded
NOTE: recipe inotify-tools-3.14-r2: task do_configure: Succeeded
NOTE: recipe vdc-ui-doorbird-git-r2: task do_compile: Succeeded
NOTE: recipe vdc-ui-panasonic-git-r3: task do_compile: Succeeded
NOTE: Tasks Summary: Attempted 5002 tasks of which 4905 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 5 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

bitbake returned 1, manual interaction required!

Build step 'Execute shell' marked build as failure
Not sending mail to unregistered user jin at developer.digitalstrom.org
Not sending mail to unregistered user Krzysztof.Michonski at digitalstrom.com
Not sending mail to unregistered user andreas.fenkart at dev.digitalstrom.org
Not sending mail to unregistered user jean.visagie at digitalstrom.com