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

[dS Jenkins]

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

Changes:

[Krzysztof.Michonski] rootfs: kernel: update srcrev

------------------------------------------
[...truncated 142.36 KB...]
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/makeshell.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/alias.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/boolean.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/usage.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/text_mmap.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/save.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/genshell.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/env.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/check.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/enum.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/option-xat-attribute.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/load.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/reset.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/restore.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/compat/compat.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/compat/pathfind.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/autoopts/usage-txt.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/autoopts/options.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/sntp/libopts/autoopts/project.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/hopf6039.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_cmdargs.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/audio.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_fp.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntpd.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/vint64ops.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_machine.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/libntp.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_stdlib.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_crypto.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/intreswork.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_syslog.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_libopts.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/icom.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/libssl_compat.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_types.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_calendar.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_config.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntpsim.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_refclock.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/refclock_atom.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/declcond.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/l_stdlib.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_random.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/timespecops.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_request.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/safecast.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_lineedit.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_worker.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_io.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_lists.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_control.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/lib_strbuf.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/recvbuff.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/timevalops.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_keyacc.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_rfc2553.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_filegen.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/rc_cmdlength.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_net.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/include/ntp_intres.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/util/tickadj.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/util/ntp-keygen-opts.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/util/ntp-keygen.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/util/ntptime.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/util/ntp-keygen-opts.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/sha1.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/buffer.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/lib.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/result.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/netaddr.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/backtrace.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/log.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/assertions.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/tsmemcmp.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/backtrace-emptytbl.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/random.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/error.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/dir.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/file.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/net.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/errno2result.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/time.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/strerror.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/ifiter_getifaddrs.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/stdio.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/errno2result.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/interfaceiter.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/include/isc/dir.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/include/isc/net.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/include/isc/offset.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/include/isc/time.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/include/isc/int.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/unix/include/isc/strerror.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/nls/msgcat.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/lib.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/buffer.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/sockaddr.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/stdio.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/string.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/random.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/boolean.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/msgcat.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/sha1.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/assertions.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/region.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/magic.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/result.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/types.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/netaddr.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/file.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/interfaceiter.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/backtrace.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/log.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/include/isc/error.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/pthreads/mutex.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/pthreads/include/isc/mutex.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/lib/isc/pthreads/include/isc/once.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/build/ntpdc/version.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/build/ntpdate/version.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/build/ntpd/version.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/build/ntpq/version.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/build/sntp/version.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/build/util/version.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/sbin/.debug/ntpdc is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/sbin/.debug/ntpdate is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/sbin/.debug/ntptime is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/sbin/.debug/tickadj is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/sbin/.debug/ntpq is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/sbin/.debug/ntp-keygen is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/sbin/.debug/sntp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-dbg/usr/sbin/.debug/ntpd.ntp 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: ntp-4.2.8p11-r0 do_package_qa: QA Issue: ntp: /ntpdate/usr/sbin/ntpdate is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntpdate/etc/default/ntpdate 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 lttng-ust-2_2.10.1-r0: task do_populate_sysroot: Succeeded
NOTE: Running task 3941 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-kernel/lttng/lttng-ust_2.10.1.bb:do_package)
WARNING: ntp-4.2.8p11-r0 do_package_qa: QA Issue: ntp: /sntp/usr/sbin/sntp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /sntp/etc/default/sntp 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: ntp-4.2.8p11-r0 do_package_qa: QA Issue: ntp: /ntp/usr/sbin/ntpd.ntp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp/etc/ntp.conf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp/etc/init.d/ntpd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp/etc/default/ntpclient is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_package: Started
NOTE: recipe ntp-4.2.8p11-r0: task do_package_qa: Succeeded
NOTE: Running task 3949 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/ds485p/ds485p_git.bb:do_install)
NOTE: recipe ds485p-git-r5: task do_install: Started
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_package_qa: Succeeded
NOTE: Running task 3950 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_fetch)
NOTE: recipe rescue-install-git-r2: task do_fetch: Started
NOTE: recipe ds485p-git-r5: task do_install: Succeeded
NOTE: Running task 3951 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/ds485p/ds485p_git.bb:do_populate_sysroot)
NOTE: recipe ds485p-git-r5: task do_populate_sysroot: Started
NOTE: recipe ds485p-git-r5: task do_populate_sysroot: Succeeded
NOTE: Running task 3952 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/ds485p/ds485p_git.bb:do_package)
NOTE: recipe ds485p-git-r5: task do_package: Started
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_package_write_ipk: Succeeded
NOTE: Running task 3953 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-devtools/xmlrpc-c/xmlrpc-c_1.39.12.bb:do_rm_work)
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_rm_work: Started
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_rm_work: Succeeded
NOTE: Running noexec task 3954 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-devtools/xmlrpc-c/xmlrpc-c_1.39.12.bb:do_rm_work_all)
NOTE: Running noexec task 3955 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-devtools/xmlrpc-c/xmlrpc-c_1.39.12.bb:do_build)
NOTE: Running task 3957 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_prepare_recipe_sysroot)
NOTE: recipe libupnp-1.6.19-r2: task do_prepare_recipe_sysroot: Started
NOTE: recipe libupnp-1.6.19-r2: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 3961 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_configure)
NOTE: recipe rescue-install-git-r2: task do_fetch: Succeeded
NOTE: Running task 3962 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_prepare_recipe_sysroot)
NOTE: recipe libupnp-1.6.19-r2: task do_configure: Started
NOTE: recipe rescue-install-git-r2: task do_prepare_recipe_sysroot: Started
NOTE: recipe systembackup-git-r1: task do_configure: Succeeded
NOTE: recipe ntp-4.2.8p11-r0: task do_package_write_ipk: Succeeded
NOTE: Running task 3963 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-bsp-ds/systembackup/systembackup_git.bb:do_compile)
NOTE: Running task 3964 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-support/ntp/ntp_4.2.8p11.bb:do_rm_work)
NOTE: recipe rescue-install-git-r2: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 3965 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_unpack)
NOTE: recipe systembackup-git-r1: task do_compile: Started
NOTE: recipe rescue-install-git-r2: task do_unpack: Started
NOTE: recipe ntp-4.2.8p11-r0: task do_rm_work: Started
NOTE: recipe systembackup-git-r1: task do_compile: Succeeded
NOTE: Running task 3966 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-bsp-ds/systembackup/systembackup_git.bb:do_install)
NOTE: recipe systembackup-git-r1: task do_install: Started
NOTE: recipe rescue-install-git-r2: task do_unpack: Succeeded
NOTE: Running task 3967 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_patch)
NOTE: recipe rescue-install-git-r2: task do_patch: Started
NOTE: recipe rescue-install-git-r2: task do_patch: Succeeded
NOTE: Running task 3968 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_populate_lic)
NOTE: recipe systembackup-git-r1: task do_install: Succeeded
NOTE: Running task 3969 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-bsp-ds/systembackup/systembackup_git.bb:do_populate_sysroot)
NOTE: recipe ntp-4.2.8p11-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 3970 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-support/ntp/ntp_4.2.8p11.bb:do_rm_work_all)
NOTE: Running noexec task 3971 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-support/ntp/ntp_4.2.8p11.bb:do_build)
NOTE: Running task 3972 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-bsp-ds/systembackup/systembackup_git.bb:do_package)
NOTE: recipe rescue-install-git-r2: task do_populate_lic: Started
NOTE: recipe systembackup-git-r1: task do_populate_sysroot: Started
NOTE: recipe systembackup-git-r1: task do_package: Started
NOTE: recipe rescue-install-git-r2: task do_populate_lic: Succeeded
NOTE: Running task 3973 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_configure)
NOTE: recipe rescue-install-git-r2: task do_configure: Started
NOTE: recipe rescue-install-git-r2: task do_configure: Succeeded
NOTE: Running task 3974 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_compile)
NOTE: recipe systembackup-git-r1: task do_populate_sysroot: Succeeded
NOTE: Running task 3976 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libpagekite/libpagekite_git.bb:do_prepare_recipe_sysroot)
NOTE: recipe rescue-install-git-r2: task do_compile: Started
NOTE: recipe libpagekite-git-r4: task do_prepare_recipe_sysroot: Started
NOTE: recipe rescue-install-git-r2: task do_compile: Succeeded
NOTE: Running task 3977 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_check_image_size)
NOTE: recipe rescue-install-git-r2: task do_check_image_size: Started
NOTE: recipe rescue-install-git-r2: task do_check_image_size: Succeeded
NOTE: Running task 3978 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install)
NOTE: recipe libpagekite-git-r4: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 3982 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libpagekite/libpagekite_git.bb:do_configure)
NOTE: recipe libpagekite-git-r4: task do_configure: Started
NOTE: recipe rescue-install-git-r2: task do_install: 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.27472)
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.27472
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-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', 'virtual:native:/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.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: ['gcc-cross-arm', 'glibc', 'quilt-native', 'u-boot-mkimage-native', 'gcc-runtime', 'libtool-native', 'autoconf-native', 'automake-native', 'xz-native', 'gnu-config-native', 'mpfr-native', 'texinfo-dummy-native', 'binutils-cross-arm', 'flex-native', 'zlib-native', 'linux-libc-headers', 'libmpc-native', 'gmp-native', 'openssl-native', 'libgcc', 'm4-native', 'gettext-minimal-native', 'bison-native', 'coreutils-native', 'pkgconfig-native', 'attr-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| awk: fatal: cannot open file `/home/****/workspace/yocto/poky-devel-nopkg-build/build/work/dss20-poky-linux-gnueabi/rescue-install/git-r2/git/dss20/rescue-initramfs/desc' for reading (No such file or directory)
| WARNING: /home/****/workspace/yocto/poky-devel-nopkg-build/build/work/dss20-poky-linux-gnueabi/rescue-install/git-r2/temp/run.do_install.27472: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.27472)
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 addon-framework-git-r2: task do_package: Succeeded
NOTE: recipe ds485p-git-r5: task do_package: Succeeded
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_package: Succeeded
NOTE: recipe systembackup-git-r1: task do_package: Succeeded
NOTE: recipe linux-5.1.7-5.1.7-r0: task do_unpack: Succeeded
NOTE: recipe libupnp-1.6.19-r2: task do_configure: Succeeded
NOTE: recipe libpagekite-git-r4: task do_configure: Succeeded
NOTE: Tasks Summary: Attempted 3983 tasks of which 3927 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 7 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 andreas.fenkart at dev.digitalstrom.org
Not sending mail to unregistered user Krzysztof.Michonski at digitalstrom.com
Not sending mail to unregistered user jin at developer.digitalstrom.org