10926 2017-01-14 00:20:52 +0000 Buildhistory fails to write to repo on new cluster 2017-07-19 21:55:46 +0000 1 1 5 Infrastructure AutoBuilder autobuilder unspecified x86 Multiple RESOLVED FIXED Medium+ normal 2.4 M2 11814 1 stephano stephano infras.ab.watcher Infras.watcher joshuagloe leonardo.sandoval.gonzalez pidge --- --- No (bug/feature does not impact docs) oldest_to_newest 69813 0 stephano 2017-01-14 00:20:52 +0000 While the builds all look like they are succeeding, and the buildhistory logs appear to be written, the following error is being displayed at the end of each build: NOTE: Writing buildhistory fatal: '//home/pokybuild/buildhistory' does not appear to be a git repository fatal: Could not read from remote repository. e.g. https://autobuilder.yocto.io/builders/nightly-x86-lsb/builds/136/steps/BuildImages/logs/stdio 69823 1 joshuagloe 2017-01-16 12:50:54 +0000 I believe there are two issues here: 1) there's a configuration issue in that the autobuilder configuration points to a non-existent repository as the buildhistory remote 2) when the buildhistory push fails the buildstep isn't marked as failed 72452 2 joshuagloe 2017-04-13 10:56:53 +0000 *** Bug 11334 has been marked as a duplicate of this bug. *** 72475 3 joshuagloe 2017-04-13 15:22:43 +0000 Too late to patch AB for 2.3 at this point, let's punt to 2.4 M1 74943 4 stephano 2017-07-11 22:44:18 +0000 I changed the configs on all the slaves and for some reason had to restart the controller to get the right variables to populate. I'm not sure what was going on there, but I'll keep an eye on the CreateAutoConf steps to be sure this is fixed. So far that step has completed on debian-testing just fine with nightly-arm. The bit that was failing was the git ls-remote: https://autobuilder.yocto.io/builders/nightly-arm/builds/400/steps/CreateAutoConf/logs/stdio (git ls-remote --exit-code file:////home/pokybuild/buildhistory) Note that BUILD_HISTORY_DIR was set correctly there after I updated the config, but was being ignored for some reason. I restarted the controller and it seems to work now: https://autobuilder.yocto.io/builders/nightly-arm/builds/401/steps/CreateAutoConf/logs/stdio (git ls-remote --exit-code ssh://git@git.yoctoproject.org/poky-buildhistory) One thing we have to decide is if we want this to be a hard error in the future. Currently it does not fail because, as mentioned, the git push is buried in an if statement with no error handling around it, so it simply never falls into the "then" clause. See CreateAutoConf.py around line 266. I'll leave this as "in progress review" until we have time to discuss how we want to deal with these types of failures.