The build results pages such as https://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/105/steps/BuildImages_3 provide access to the stdio log that shows an autobuilder failure. The configuration that led to the failure, though, is not easily available: the only solution I've found is to clone the autobuilder infrastructure, install a local buildbot, and attempt to reconstruct the auto.conf file that the infrastructure would create. This is prone to mistakes that result in inconsistent builds that muddy the issue even more. Would it be possible to add a link on the build page, similar to the one for stdio, that provides sufficient configuration information (local.conf/auto.conf/bblayers.conf, possibly repo URL and commit SHA1) that somebody could reproduce the failure outside the autobuilder infrastructure?
If you look at the steps, there is an auto.conf creation step, which shows exactly what is being put into the file. If you look at the step https://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/105/steps/CreateAutoConf/logs/stdio it show the contents of the auto.conf being creeated (see below). There is also a step for bblayers creation: https://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/105/steps/Create%20BBLayers%20Configuration/logs/stdio sh -c 'rm -rf ./build/conf/auto.conf; printf '"'"'INHERIT += "report-error" DISTRO = "poky" PACKAGE_CLASSES = "package_rpm package_deb package_ipk" BB_NUMBER_THREADS = "16" PARALLEL_MAKE = "-j 16" SDKMACHINE ?= "x86_64" BB_TASK_NICE_LEVEL = "5" IMAGE_FSTYPES_append = " tar.gz" BB_TASK_NICE_LEVEL_task-testimage = "0" DL_DIR = "/srv/www/vhosts/autobuilder.yoctoproject.org/current_sources" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" SSTATE_DIR ?= "/srv/www/vhosts/autobuilder.yoctoproject.org/pub/sstate/multilib" MACHINE = "qemux86-64" PREMIRRORS = "" BB_GENERATE_MIRROR_TARBALLS = "1" ADTREPO = "http://adtrepo.yoctoproject.org//1.7" '"'"'>> ./build/conf/auto.conf'
Thanks; I wasn't aware that each step had its own output file though now I know to look for it it's obvious.