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

[dS Jenkins]

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

Changes:

[jean.visagie] Try own sstatecache for each platform

------------------------------------------
[...truncated 108.36 KB...]
ntp: /ntp-doc/usr/share/doc/ntp/html/hints/winnt.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver10.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver44.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/oncore-shmem.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver28.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver19.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver5.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver29.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver3.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver30.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver45.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver11.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver33.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver16.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver12.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver39.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver43.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver20.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver4.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver26.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver32.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver38.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver18.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver40-ja.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/tf582_4.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver37.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver9.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver1.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver31.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver36.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver34.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/mx4200data.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver22.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver35.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver6.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver40.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver42.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver7.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver8.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver27.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/driver46.html is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/icons/home.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/icons/mail2.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/scripts/style.css is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/drivers/scripts/footer.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/audio.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/miscopt.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/install.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/config.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/monopt.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/accopt.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/manual.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/command.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/external.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/refclock.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/authopt.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/clockopt.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/special.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/hand.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/confopt.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/misc.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/style.css is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/scripts/footer.txt is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/thunderbolt.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/rabbit.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/description.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/driver43_2.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/alice31.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/boom4.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/pogo3a.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/oncore_remoteant.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/pd_om011.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/alice15.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/oncore_evalbig.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/stats.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/alice23.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/pogo4.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/tribeb.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/flt3.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/dogsnake.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/9400n.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/flt8.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/pogo1a.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/oncore_utplusbig.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/alice51.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/gadget.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/driver29.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/igclock.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/beaver.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/flt7.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/peer.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/alice47.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/alice32.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/pogo6.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/alice61.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/sheepb.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/oz2.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/alice38.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/alice13.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/offset1211.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/panda.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/sx5.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/freq1211.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/fig_3_1.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/neoclock4x.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/pogo7.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/c51.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/pogo.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/flt9.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/boom3.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/pd_om006.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/barnstable.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/alice44.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/pzf511.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/flt1.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/pogo5.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/time1.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/flt5.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/fg6039.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/radio2.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/flt2.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/boom3a.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/hornraba.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/flt4.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/alice35.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/group.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/pogo8.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/wingdorothy.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/broad.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/flatheads.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/stack1a.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/bustardfly.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/tonea.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/fg6021.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/flt6.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/pzf509.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/driver43_1.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/discipline.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/gps167.jpg is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/ntp/html/pic/alice11.gif is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-doc/usr/share/doc/sntp/sntp.html 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-utils/usr/share/ntp/lib/NTP/Util.pm is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/calc_tickadj is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/ntpdc is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/ntp-wait is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/ntptrace is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/ntptime is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/ntpq is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntp-utils/usr/sbin/ntp-keygen 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-tickadj/usr/sbin/tickadj is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: ntp-4.2.8p11-r0 do_package_qa: QA Issue: ntp: /ntpdate/usr/sbin/ntpdate is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
ntp: /ntpdate/etc/default/ntpdate is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: recipe rrdtool-1.6.0-r0: task do_install: Succeeded
NOTE: Running task 3837 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-oe/recipes-extended/rrdtool/rrdtool_1.6.0.bb:do_populate_sysroot)
NOTE: recipe ntp-4.2.8p11-r0: task do_package_qa: Succeeded
NOTE: Running task 3838 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-oe/recipes-extended/rrdtool/rrdtool_1.6.0.bb:do_package)
NOTE: recipe dss11-websetup-git-r1: task do_package_qa: Succeeded
NOTE: Running task 3942 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-kernel/lttng/lttng-ust_2.10.1.bb:do_install)
NOTE: recipe rrdtool-1.6.0-r0: task do_populate_sysroot: Started
NOTE: recipe rrdtool-1.6.0-r0: task do_package: Started
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_install: Started
NOTE: recipe rrdtool-1.6.0-r0: task do_populate_sysroot: Succeeded
NOTE: Running task 3951 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-devtools/xmlrpc-c/xmlrpc-c_1.39.12.bb:do_populate_sysroot)
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_populate_sysroot: Started
NOTE: recipe dss11-websetup-git-r1: task do_package_write_ipk: Succeeded
NOTE: Running task 3952 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dss11-websetup/dss11-websetup_git.bb:do_rm_work)
NOTE: recipe dss11-websetup-git-r1: task do_rm_work: Started
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_populate_sysroot: Succeeded
NOTE: Running task 3953 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-devtools/xmlrpc-c/xmlrpc-c_1.39.12.bb:do_package)
NOTE: recipe xmlrpc-c-1.39.12-r2: task do_package: Started
NOTE: recipe dss11-websetup-git-r1: task do_rm_work: Succeeded
NOTE: Running task 3961 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/ds485p/ds485p_git.bb:do_install)
NOTE: recipe ds485p-git-r5: task do_install: Started
NOTE: recipe ds485p-git-r5: task do_install: Succeeded
NOTE: Running task 3962 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/ds485p/ds485p_git.bb:do_populate_sysroot)
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_install: Succeeded
NOTE: Running task 3963 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-kernel/lttng/lttng-ust_2.10.1.bb:do_populate_sysroot)
NOTE: recipe ds485p-git-r5: task do_populate_sysroot: Started
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_populate_sysroot: Started
NOTE: recipe ds485p-git-r5: task do_populate_sysroot: Succeeded
NOTE: Running task 3964 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/ds485p/ds485p_git.bb:do_package)
NOTE: recipe ds485p-git-r5: task do_package: Started
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_populate_sysroot: Succeeded
NOTE: Running task 3965 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-kernel/lttng/lttng-ust_2.10.1.bb:do_package)
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_package: Started
NOTE: recipe rrdtool-1.6.0-r0: task do_package: Succeeded
NOTE: recipe ntp-4.2.8p11-r0: task do_package_write_ipk: Succeeded
NOTE: Running task 3966 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-oe/recipes-extended/rrdtool/rrdtool_1.6.0.bb:do_packagedata)
NOTE: Running task 3967 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-support/ntp/ntp_4.2.8p11.bb:do_rm_work)
NOTE: recipe ntp-4.2.8p11-r0: task do_rm_work: Started
NOTE: recipe rrdtool-1.6.0-r0: task do_packagedata: Started
NOTE: recipe strace-4.20-r0: task do_package_write_ipk: Succeeded
NOTE: Running task 3976 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-rescue/rescue-install/rescue-install_git.bb:do_install)
NOTE: recipe rpm-1_4.14.1-r0: task do_install: Succeeded
NOTE: Running task 3977 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/rpm/rpm_4.14.1.bb:do_populate_sysroot)
NOTE: recipe ntp-4.2.8p11-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 3978 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-support/ntp/ntp_4.2.8p11.bb:do_rm_work_all)
NOTE: Running noexec task 3979 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-networking/recipes-support/ntp/ntp_4.2.8p11.bb:do_build)
NOTE: Running noexec task 3980 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dss11-websetup/dss11-websetup_git.bb:do_rm_work_all)
NOTE: Running noexec task 3981 of 6714 (/home/****/workspace/yocto/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dss11-websetup/dss11-websetup_git.bb:do_build)
NOTE: Running task 3982 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/rpm/rpm_4.14.1.bb:do_package)
NOTE: recipe rrdtool-1.6.0-r0: task do_packagedata: Succeeded
NOTE: Running task 3983 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-oe/recipes-extended/rrdtool/rrdtool_1.6.0.bb:do_package_qa)
NOTE: recipe rescue-install-git-r2: task do_install: Started
NOTE: recipe rpm-1_4.14.1-r0: task do_populate_sysroot: Started
NOTE: recipe rpm-1_4.14.1-r0: task do_package: Started
NOTE: recipe rrdtool-1.6.0-r0: task do_package_qa: 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.6926)
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.6926
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['virtual:native:/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-core/glibc/glibc_2.27.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/gcc/gcc-runtime_7.3.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/gcc/gcc-cross_7.3.bb:do_populate_sysroot', 'virtual:native:/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot', '/home/****/workspace/yocto/yocto/feedconfig/devel/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['u-boot-mkimage-native', 'glibc', 'gcc-runtime', 'gcc-cross-arm', 'pseudo-native', 'quilt-native', 'openssl-native', 'linux-libc-headers', 'texinfo-dummy-native', 'libtool-native', 'gnu-config-native', 'binutils-cross-arm', 'libmpc-native', 'automake-native', 'autoconf-native', 'mpfr-native', 'xz-native', 'flex-native', 'gmp-native', 'zlib-native', 'libgcc', 'pkgconfig-native', 'bison-native', 'm4-native', 'gettext-minimal-native', 'coreutils-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.6926: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.6926)
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: Running task 3984 of 6714 (/home/****/workspace/yocto/yocto/feedconfig/devel/layers/meta-openembedded/meta-oe/recipes-extended/rrdtool/rrdtool_1.6.0.bb:do_package_write_ipk)
NOTE: recipe rrdtool-1.6.0-r0: task do_package_write_ipk: Started
NOTE: recipe rrdtool-1.6.0-r0: task do_package_qa: Succeeded
NOTE: recipe rpm-1_4.14.1-r0: task do_populate_sysroot: Succeeded
NOTE: recipe ds485p-git-r5: task do_package: Succeeded
NOTE: recipe rrdtool-1.6.0-r0: task do_package_write_ipk: Succeeded
NOTE: recipe lttng-ust-2_2.10.1-r0: task do_package: Succeeded
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 rpm-1_4.14.1-r0: task do_package: Succeeded
NOTE: Tasks Summary: Attempted 3984 tasks of which 3953 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 jin at developer.digitalstrom.org
Not sending mail to unregistered user Krzysztof.Michonski at digitalstrom.com
Not sending mail to unregistered user andreas.fenkart at dev.digitalstrom.org
Not sending mail to unregistered user jean.visagie at digitalstrom.com