10779 2016-12-08 15:28:16 +0000 Ensure auto.conf is restored at the end of build steps which modify it 2018-03-22 08:48:09 +0000 1 1 5 Infrastructure AutoBuilder autobuilder 2.3 x86 Multiple RESOLVED FIXED Medium enhancement 2.5 1 joshuagloe joshuagloe infras.ab.watcher Infras.watcher pidge --- --- No (bug/feature does not impact docs) oldest_to_newest 68936 0 joshuagloe 2016-12-08 15:28:16 +0000 Several build steps modify auto.conf which may then have a knock-on effect on later build steps. We should restore the auto.conf to the default state, as created by the CreateAutoConf step, at the end of buildsteps which modify it in order to ensure the environment for the build is as expected. Such a change was already made to RunSanityTests in order to resolve issues in the jethro build: http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder/commit/?id=e675e6a7e8d06dcd0141394f329b74c2f5da21fa but this should be generalised and used more widely post M1. 68961 1 joshuagloe 2016-12-08 21:15:53 +0000 The change to RunSanityTests had to be reverted because it was causing exceptions on several of the builders on the YP cluster: http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder/commit/?id=b5007ccf74e6f31c419a0b6b06f467ab9c9379b7 79925 2 joshuagloe 2018-03-22 08:48:09 +0000 Effectively resolved by the new infrastructure architecture of helper scripts (yocto-autobuilder-helper) with a more recent buildbot with minimal configuration (yocto-autobuilder2).