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

[dS Jenkins]

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

Changes:

[Krzysztof.Michonski] testing: rescue: sync with devel

------------------------------------------
[...truncated 619.82 KB...]
strace: /strace-ptest/usr/lib/strace/ptest/tests/statfs64 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/sigaction.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/quotactl-v is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/setgroups32.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/netlink_selinux.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/prlimit64 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/symlinkat.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/quotactl-xfs is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/pread64-pwrite64.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/print_maxfd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/prctl-seccomp-strict is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/oldfstat is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/execve-v.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ioctl-v.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ioctl_evdev.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nfnetlink_acct is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/alarm is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/attach-p-cmd-cmd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/finit_module.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/strace-r.expected is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/mq_sendrecv-write is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/sendfile64.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/splice.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ioperm.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/lookup_dcookie is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/xchownx.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/xet_robust_list.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/dup.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/prctl-securebits.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/get_mempolicy.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/rt_sigpending.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/netlink_crypto is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/sethostname is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/kexec_load.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/link is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/int_0x80.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/run.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_br_port_msg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ioctl_mtd.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/setfsgid is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/accept4 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/chown32.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/detach-sleeping.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/keyctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/renameat is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ioctl_block is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/getresuid32.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/request_key.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/signal is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ioctl_rtc-v is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/pc is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/munlockall.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/fstatat.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/preadv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/netlink_selinux is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/fanotify_mark.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/qual_fault.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/mknod is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/fork-f.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/getresugid.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/wait4 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nfnetlink_cthelper.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/getrusage is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/btrfs-vw.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/sync_file_range.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/lseek.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/int_0x80 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/sched.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/statx.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/setfsugid.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/msg_control.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/mount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/iopl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/epoll_ctl is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/clone_parent.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/geteuid32.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ioctl_sg_io_v4.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/timer_create is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/prctl-pdeathsig.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/newfstatat.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/select is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/net-yy-unix.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/creat is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/kill.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/pwritev.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/trace_stat_like.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/redirect-fds is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/setfsuid32 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/netlink_inet_diag is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/readdir is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/sync_file_range is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/file_handle.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/xattr-strings is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ipc_msg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/epoll_create.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/umoven-illptr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/openat is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_netconfmsg.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/getrandom.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/mmsg_name-v.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/getgid is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/qual_signal.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/rmdir.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ip_mreq.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/clock.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/membarrier.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ipc.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/printstrn-umoven-undumpable is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/lstatx.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/fsync is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/quotactl.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/getcwd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/filter-unavailable.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_mdba_router_port.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/oldlstat is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/reboot is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/msg_control-v is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/redirect.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/xattr.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/unshare.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/getgroups is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/quotactl-xfs-v.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/setresgid32.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ptrace is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/netlink_sock_diag is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ioctl_loop-v.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/mmsg_name-v is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/chroot is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/sigprocmask.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ioprio is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/fadvise64.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/xutimes.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_crypto_user_alg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/prlimit64.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/sigpending.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/mmap64 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/setresgid32 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ppoll-v is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/xstatx.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/net-yy-inet.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/iopl.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/sched_xetattr.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/mmap is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/sync is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/setreuid32 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/rename.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/waitid-v is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ipc_sem.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/move_pages is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/netlink_netlink_diag is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/wait4.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/keyctl.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/printpath-umovestr-undumpable is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/mmsg_name.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ftruncate64.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_crypto_user_alg.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/so_peercred.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/group_req is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/preadv2-pwritev2.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/sched_xetparam.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ioctl_sg_io_v3.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/ppoll.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/strace-r.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_nlmsgerr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/vfork-f is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/adjtimex.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/fstatfs.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/init_module.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/net-yy-inet is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/sigsuspend is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/seccomp-strict is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/times is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/getxxid is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/fstatat64 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/truncate64.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/mmsg.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/fflush is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/trace_question.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/setregid.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_mdba_mdb_entry is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/get_mempolicy is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/net-y-unix is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nfnetlink_nftables is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/alarm.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_rtgenmsg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/setuid is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/netlink_xfrm.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/init.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/qual_signal is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/mmsg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_ifaddrlblmsg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/setgroups32 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/netlink_kobject_uevent.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/migrate_pages is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/strace-V.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/caps-abbrev is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/execveat is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/perf_event_open.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/swap is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/net.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/getpgrp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nfnetlink_ctnetlink_exp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/semop is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/perf_event_open_unabbrev.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/pread64-pwrite64 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/clone_ptrace.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/sched_xetaffinity is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/perf_event_open_nonverbose is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/kill is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_ndmsg.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/umovestr-illptr is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_ifla_brport is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_br_port_msg.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_packet_diag_msg.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/times.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/futimesat is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/rt_sigaction is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/strace-S.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/getuid32.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/stack-fcall is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/mq_sendrecv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/oldstat.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_fib_rule_hdr.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/nlattr_mdba_mdb_entry.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/printpath-umovestr.gen.test is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/umount is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace-ptest/usr/lib/strace/ptest/tests/getdents64.gen.test 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: strace-4.20-r0 do_package_qa: QA Issue: strace: /strace/usr/bin/strace-log-merge is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
strace: /strace/usr/bin/strace 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 xmlrpc-c-1.39.12-r2: task do_package: Succeeded
NOTE: recipe strace-4.20-r0: task do_package_qa: Succeeded
NOTE: recipe ds485p-git-r5: task do_configure: Succeeded
NOTE: recipe ntp-4.2.8p11-r0: task do_install: Succeeded
NOTE: Tasks Summary: Attempted 3975 tasks of which 3751 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 4 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

bitbake returned 1, manual interaction required!

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