I'm seeing the following issue: (only tested on edison so far). Seems likely to be a multithreaded issues as it rarely occurs on my build box NOTE: package xf86bigfontproto-1_1.2.0-r1: task do_package_setscene: Started NOTE: package e2fsprogs-1.41.14-r1: task do_package_setscene: Succeeded NOTE: package pango-1.28.4-r1: task do_populate_sysroot_setscene: Started NOTE: Running setscene task 1504 of 1694 (/opt/yocto/cache-build/p4080ds/meta/recipes-core/udev/udev_164.bb:do_package_setscene) NOTE: package libgcrypt-1.4.6-r1: task do_populate_sysroot_setscene: Started NOTE: package libxcomposite-1_0.4.3-r0: task do_populate_sysroot_setscene: Started NOTE: package libxml-parser-perl-native-2.40-r4: task do_populate_sysroot_setscene: Started NOTE: package xcmiscproto-1_1.2.1-r0: task do_package_setscene: Succeeded NOTE: package util-linux-2.19.1-r9: task do_package_setscene: Succeeded NOTE: Running setscene task 1505 of 1694 (/opt/yocto/cache-build/p4080ds/meta/recipes-core/glib-2.0/glib-2.0_2.28.8.bb:do_package_setscene) NOTE: package gzip-native-1.4-r0: task do_populate_sysroot_setscene: Succeeded NOTE: Running setscene task 1506 of 1694 (/opt/yocto/cache-build/p4080ds/meta/recipes-graphics/drm/libdrm_2.4.26.bb:do_populate_sysroot_setscene) NOTE: package gdk-pixbuf-2.22.1-r1: task do_populate_sysroot_setscene: Succeeded NOTE: Running setscene task 1507 of 1694 (/opt/yocto/cache-build/p4080ds/meta/recipes-graphics/fontconfig/fontconfig_2.8.0.bb:do_package_setscene) NOTE: Running setscene task 1508 of 1694 (/opt/yocto/cache-build/p4080ds/meta/recipes-graphics/xorg-lib/libsm_1.2.0.bb:do_populate_sysroot_setscene) NOTE: package gdbm-1.8.3-r4: task do_populate_sysroot_setscene: Started ERROR: Task 3549 (/opt/yocto/cache-build/p4080ds/meta/recipes-graphics/xorg-proto/xf86bigfontproto_1.2.0.bb, do_package_setscene) failed with exit code '1'
Created attachment 283 [details] console out on failure
Is this still happening for you? I don't see this here and to be able to figure anything further out I need the do_package_setscene logs from the xf86bigfontproto temp directory (from its WORKDIR) to see what the failure was.
(In reply to comment #2) > Is this still happening for you? I don't see this here and to be able to figure > anything further out I need the do_package_setscene logs from the > xf86bigfontproto temp directory (from its WORKDIR) to see what the failure was. This just happened last night... I've been running 2 builds concurrently for about a week and this is the first I've seen of it... -M
Please ignore my "is this still happening" question, I misread the timestamp on the bug. The request for a logfile stands. It would be useful if you could reproduce this against master too given the number of changes in this area that have taken place there.
Specific build logs are gone now.... Should'nt bitbake spit out this build failure to the console? It does so for compile/configure/install.... -M
(In reply to comment #4) > Please ignore my "is this still happening" question, I misread the timestamp on > the bug. The request for a logfile stands. It would be useful if you could > reproduce this against master too given the number of changes in this area that > have taken place there. I'll let you know if I see it on master... but resources are thin and I don't even remember the last time I built master =( -M
"setscene" functions are optional in that if they fail, we'll just build the failed component. We don't really want to scare the user with scary failures with things then magically working which is why the bitbake exit code isn't affected either. So I think its behaving as designed although in this case it likely does mean we've lost the useful logfile :(
I'm going to close this since I have no way to fix this based on the current information. If you see it again and get a log file please reopen and we'll see if we can figure out whats going on.