On Sun, Feb 14, 2021 at 6:19 AM Richard Purdie <[email protected]> wrote: > > Regular users of the autobuilder will note that I've split the > reproducible builds test out of the main oe-selftest build and into its > own target build. This is because that test tends to run for a lot > longer time period and it helps to see the result separately. > > I've only done this for master. If gatesgarth and dunfell want to > follow, that should be straight forward with a change to the branch in > autobuilder-helper. Obviously we should ensure this is working ok with > master first but so far so good. > > It has already highlighted the difference between a successful run: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/115/builds/2 > https://autobuilder.yoctoproject.org/typhoon/#/builders/119/builds/2 > (took 3-4 hours) > > and failing two failing runs: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/116/builds/2 > https://autobuilder.yoctoproject.org/typhoon/#/builders/118/builds/2 > (took 9 hours)
OK, I read through the code and unfortunately found a bug: when attempting to make sure the "B" build doesn't use sstate, I misspelled the SSTATE_MIRRORS, which means that the B build could have been pulling from the sstate mirror when it was not supposed to. This has a few implications: 1) It might explain why some of the reproducible results seem intermittent 2) It might explain why there is such a time disparity between the tests Unfortunately, while it probably will help the intermittent results, it probably means that the tests taking 9 hours is what is "supposed" to happen, and they happen to be shorter sometimes because the B build is pulling from sstate when it's not supposed to. > > the time difference being the system trying to run diffoscope on vim- > common :/. > > I'm aware I removed some recipes from the exclusions list after seeing > multiple passing builds for all distros and we're now seeing test > failures. My mistake was not waiting for the date to change and for > builds to run on an autobuilder worker with a different umask. > > Meson is failing with a pyc file mismatch which diffoscope can't decode > and despite trying for 5 hours, diffoscope hasn't given any data on why > vim-common differs. I should have fixes in for quilt, valgrind, kernel- > devsrc and cwautomacros. The umask fix may fix other issues too. Alex > has improved the reporting so we can spot cases where exclusion is now > longer needed. > > Cheers, > > Richard >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#148040): https://lists.openembedded.org/g/openembedded-core/message/148040 Mute This Topic: https://lists.openembedded.org/mt/80629232/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
