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

[dS Jenkins]

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

Changes:

[Krzysztof.Michonski] rescue: ledd: fix switch case

------------------------------------------
[...truncated 62.17 KB...]
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ust-elf.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-probes.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ring-buffer-client.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/tracelog.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-pthread-id.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/jhash.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-vtid.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-rb-clients.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ust-statedump.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-procname.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/getenv.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/ust-core.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/tracepoint-internal.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/perf_event.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-clock.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ust-comm.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ust-dynamic-type.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/string-utils.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/string-utils.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-perf-counters.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/getenv.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-ust-abi.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/ust_lib.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/tracepoint-weak-test.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-ip.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/tracepoint.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-context-provider.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/error.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/tracef.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/filter-bytecode.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust/lttng-filter-interpreter.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/ust-comm.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/ust-fd.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/share.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/usterr-signal-safe.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/helper.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-dlfcn.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/lttng-ust-tracelog.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/tracepoint.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-context-provider.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-abi.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-ctl.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-elf.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-error.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-tracepoint-event.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/lttng-ust-tracef.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/tracepoint-types.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ringbuffer-config.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-dynamic-type.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-events.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust-tid.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/include/lttng/ust.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/backend_internal.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/ring_buffer_frontend.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/vatomic.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/shm_types.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/backend_types.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/getcpu.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/frontend.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/rb-init.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/shm.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/backend.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/frontend_internal.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/shm_internal.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/smp.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/shm.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/ring_buffer_backend.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/frontend_types.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/smp.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/libringbuffer/frontend_api.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-comm/lttng-ust-fd-tracker.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-comm/lttng-ust-comm.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-libc-wrapper/ust_libc.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-libc-wrapper/lttng-ust-malloc.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-libc-wrapper/ust_pthread.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-libc-wrapper/lttng-ust-pthread.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/src/debug/lttng-ust/2_2.10.1-r0/lttng-ust-2.10.1/liblttng-ust-fork/ustfork.c is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-libc-wrapper.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-fd.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-cyg-profile-fast.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-pthread-wrapper.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-fork.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-dl.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-tracepoint.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-cyg-profile.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust-ctl.so.4.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dbg/usr/lib/.debug/liblttng-ust.so.0.0.0 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 ds485p-git-r5: task do_populate_sysroot: Started
WARNING: lttng-ust-2_2.10.1-r0 do_package_qa: QA Issue: lttng-ust: /lttng-ust-dev/usr/include/lttng/align.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/tracepoint-rcu.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-endian.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-tracer.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/lttng-ust-tracelog.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-version.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/tracepoint.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-getcpu.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-abi.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-tracepoint-event-nowrite.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/tracelog.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-ctl.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-compiler.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-tracepoint-event-write.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-elf.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-tracepoint-event-reset.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-error.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-tracepoint-event.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/lttng-ust-tracef.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-config.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/tracepoint-types.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ringbuffer-config.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-clock.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/tracepoint-event.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust-events.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/bug.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/tracef.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ringbuffer-abi.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/include/lttng/ust.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-tracepoint.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-ctl.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-dl.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-cyg-profile.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-fd.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-libc-wrapper.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-cyg-profile-fast.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-fork.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/liblttng-ust-pthread-wrapper.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust-dev/usr/lib/pkgconfig/lttng-ust.pc 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 nftables-0.7-r0: task do_install: Succeeded
NOTE: Running task 4016 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-filter/nftables/nftables_0.7.bb:do_populate_sysroot)
WARNING: lttng-ust-2_2.10.1-r0 do_package_qa: QA Issue: lttng-ust: /lttng-ust/usr/lib/liblttng-ust-cyg-profile-fast.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-libc-wrapper.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-fd.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-cyg-profile-fast.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-pthread-wrapper.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-fork.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-pthread-wrapper.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-fd.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-fork.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-dl.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-libc-wrapper.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-tracepoint.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-cyg-profile.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-cyg-profile.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-ctl.so.4.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-tracepoint.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-ctl.so.4 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust-dl.so.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
lttng-ust: /lttng-ust/usr/lib/liblttng-ust.so.0.0.0 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 libupnp-1.6.19-r2: task do_install: Succeeded
WARNING: lttng-ust-2_2.10.1-r0 do_package_qa: QA Issue: lttng-ust: /lttng-ust-bin/usr/bin/lttng-gen-tp is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: Running task 4017 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_populate_sysroot)
NOTE: recipe libpagekite-git-r4: task do_install: Succeeded
NOTE: Running task 4018 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libpagekite/libpagekite_git.bb:do_populate_sysroot)
NOTE: recipe nftables-0.7-r0: task do_populate_sysroot: Started
NOTE: recipe libupnp-1.6.19-r2: task do_populate_sysroot: Started
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_package_qa: Succeeded
NOTE: recipe ds485p-git-r5: task do_populate_sysroot: Succeeded
NOTE: recipe libpagekite-git-r4: task do_populate_sysroot: Started
NOTE: Running task 4019 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/ds485p/ds485p_git.bb:do_package)
NOTE: Running task 4020 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-filter/nftables/nftables_0.7.bb:do_package)
NOTE: recipe nftables-0.7-r0: task do_populate_sysroot: Succeeded
NOTE: Running task 4021 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libupnp/libupnp_1.6.19.bb:do_package)
NOTE: recipe nftables-0.7-r0: task do_package: Started
NOTE: recipe ds485p-git-r5: task do_package: Started
NOTE: recipe swupdate-2018.03-r0: task do_configure: Succeeded
NOTE: Running task 4022 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-connectivity/libpagekite/libpagekite_git.bb:do_package)
NOTE: recipe libupnp-1.6.19-r2: task do_package: Started
NOTE: recipe libupnp-1.6.19-r2: task do_populate_sysroot: Succeeded
NOTE: Running task 4023 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel-extra-layers/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb:do_compile)
NOTE: recipe libpagekite-git-r4: task do_package: Started
NOTE: recipe libpagekite-git-r4: task do_populate_sysroot: Succeeded
NOTE: Running task 4041 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/device-energy-collector_git.bb:do_prepare_recipe_sysroot)
NOTE: recipe swupdate-2018.03-r0: task do_compile: Started
NOTE: recipe device-energy-collector-git-r8: task do_prepare_recipe_sysroot: Started
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_package_write_ipk: Succeeded
NOTE: Running task 4042 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-kernel/lttng/lttng-ust_2.10.1.bb:do_rm_work)
NOTE: recipe device-energy-collector-git-r8: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 4046 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/device-energy-collector_git.bb:do_configure)
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_rm_work: Started
NOTE: recipe device-energy-collector-git-r8: task do_configure: Started
NOTE: recipe rescue-install-git-r2: task do_fetch: Succeeded
NOTE: Running task 4047 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_prepare_recipe_sysroot)
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 4048 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-kernel/lttng/lttng-ust_2.10.1.bb:do_rm_work_all)
NOTE: Running noexec task 4049 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-kernel/lttng/lttng-ust_2.10.1.bb:do_build)
NOTE: Running task 4050 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_unpack)
NOTE: recipe rescue-install-git-r2: task do_prepare_recipe_sysroot: Started
NOTE: recipe rescue-install-git-r2: task do_unpack: Started
NOTE: recipe rescue-install-git-r2: task do_unpack: Succeeded
NOTE: recipe rescue-install-git-r2: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 4056 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/statistic-tools/heating-controller-logger_git.bb:do_configure)
NOTE: Running task 4057 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_patch)
NOTE: recipe heating-controller-logger-git-r11: task do_configure: Started
NOTE: recipe rescue-install-git-r2: task do_patch: Started
NOTE: recipe rescue-install-git-r2: task do_patch: Succeeded
NOTE: Running task 4058 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_populate_lic)
NOTE: recipe rescue-install-git-r2: task do_populate_lic: Started
NOTE: recipe rescue-install-git-r2: task do_populate_lic: Succeeded
NOTE: Running task 4059 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 4060 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_compile)
NOTE: recipe rescue-install-git-r2: task do_compile: Started
NOTE: recipe rescue-install-git-r2: task do_compile: Succeeded
NOTE: Running task 4061 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 4062 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install)
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.24977)
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.24977
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', 'virtual:native:/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/gcc/gcc-runtime_7.3.bb:do_populate_sysroot', 'virtual:native:/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: ['pseudo-native']
| NOTE: Skipping as already exists in sysroot: ['gcc-cross-arm', 'glibc', 'u-boot-mkimage-native', 'quilt-native', 'gcc-runtime', 'linux-libc-headers', 'libmpc-native', 'automake-native', 'libtool-native', 'binutils-cross-arm', 'mpfr-native', 'texinfo-dummy-native', 'zlib-native', 'flex-native', 'gmp-native', 'xz-native', 'gnu-config-native', 'autoconf-native', 'openssl-native', 'libgcc', 'bison-native', 'gettext-minimal-native', 'coreutils-native', 'm4-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.24977: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.24977)
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 nftables-0.7-r0: task do_package: Succeeded
NOTE: recipe ds485p-git-r5: task do_package: Succeeded
NOTE: recipe libupnp-1.6.19-r2: task do_package: Succeeded
NOTE: recipe libpagekite-git-r4: task do_package: Succeeded
NOTE: recipe swupdate-2018.03-r0: task do_compile: Succeeded
NOTE: recipe device-energy-collector-git-r8: task do_configure: Succeeded
NOTE: recipe heating-controller-logger-git-r11: task do_configure: Succeeded
NOTE: Tasks Summary: Attempted 4063 tasks of which 4028 didn't need to be rerun and 1 failed.
NOTE: No commit since BUILDHISTORY_COMMIT != '1'
NOTE: Syncing deploy/images.

Summary: 1 task failed:
  /home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install
Summary: There were 5 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

bitbake returned 1, manual interaction required!

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