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

[dS Jenkins]

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

Changes:

[andreas.fenkart] rootfs: dssip: enable watchdog

------------------------------------------
[...truncated 97.27 KB...]
ntp: /ntp-dbg/usr/src/debug/ntp/4.2.8p11-r0/ntp-4.2.8p11/libntp/getopt.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/libntp/refnumtoa.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/libntp/audio.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/libntp/modetoa.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/libntp/socktohost.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/libntp/atoint.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/libntp/syssignal.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/libntp/strl_obsd.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/libntp/ntp_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/libntp/ntp_libopts.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/libntp/emalloc.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/libntp/recvbuff.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/libntp/work_thread.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/libntp/mstolfp.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/libntp/ntp_lineedit.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/libntp/caljulian.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/libntp/socket.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/libntp/dofptoa.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/libntp/prettydate.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/libntp/ssl_init.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/libntp/vint64ops.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/libntp/authreadkeys.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/libntp/hextoint.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/libntp/octtoint.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/libntp/ntp_intres.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/libntp/a_md5encrypt.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/libntp/ntp_crypto_rnd.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/libntp/authusekey.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/libntp/libssl_compat.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/libntp/atouint.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/libntp/humandate.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/libntp/findconfig.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/libntp/machines.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/libntp/ymd2yd.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/libntp/socktoa.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/libntp/uglydate.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/libntp/netof.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/libntp/numtoa.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/libntp/dolfptoa.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/libntp/caltontp.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/libntp/msyslog.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/libntp/lib_strbuf.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/libntp/ntp_rfc2553.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/libntp/ntp_calendar.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/libntp/is_ip_address.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/libntp/statestr.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/libjsmn/jsmn.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/libjsmn/jsmn.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/sntp-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/sntp/sntp-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/sntp/sntp.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/main.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/utilities.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/networking.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/networking.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/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/sntp/kod_management.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/crypto.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/kod_management.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/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/sntp/utilities.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/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/sntp/main.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/ag-char-map.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/numeric.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/find.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/ao-strs.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/nested.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/sort.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/init.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.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/ao-strs.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/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/sntp/libopts/libopts.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.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/stack.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-value-type.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/streqvcmp.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.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/putshell.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-value-type.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/pgusage.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/configfile.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/cook.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/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/sntp/libopts/tokenize.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/parse-duration.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/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/ntp-4.2.8p11/sntp/libopts/option-xat-attribute.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/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]
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 ntp-4.2.8p11-r0: task do_package_qa: Succeeded
NOTE: recipe dss11-websetup-git-r1: task do_install: Succeeded
NOTE: recipe libsolv-0.6.33-r0: task do_compile: Succeeded
NOTE: recipe ntp-4.2.8p11-r0: task do_package_write_ipk: Succeeded
NOTE: Tasks Summary: Attempted 4004 tasks of which 3985 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 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
Not sending mail to unregistered user jin at developer.digitalstrom.org