Recently we that build [1] looks the CreateAutoConf step [2] green but internally there was a problem, meaning that the status code is somehow not being checked. This is the error log observed on [2] ---snip--- Initialized empty Git repository in /srv/www/vhosts/autobuilder.yoctoproject.org/buildhistory/poky/master-next/nightly-mips/.git/ Host key verification failed. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Host key verification failed. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Switched to a new branch 'poky/master-next/nightly-mips' [poky/master-next/nightly-mips (root-commit) 509ea75] Initializing Repo Committer: Poky Build User <pokybuild@fedora25.osl.yoctoproject.org> Your name and email address were configured automatically based on your username and hostname. Please check that they are accurate. You can suppress this message by setting them explicitly. Run the following command and follow the instructions in your editor to edit your configuration file: git config --global --edit After doing this, you may fix the identity used for this commit with: git commit --amend --reset-author 1 file changed, 1 insertion(+) create mode 100644 README Host key verification failed. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ---snip--- [1] https://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/1107 [2] https://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/1107/steps/CreateAutoConf/logs/stdio
(In reply to comment #0) > Recently we that build [1] looks the CreateAutoConf step [2] green but > internally there was a problem, meaning that the status code is somehow not > being checked. Sorry for the wording, re-phrasing: In a recent build [1], the step CreateAutoConf [2] is green but internally there was a problem, meaning that the status code is somehow not being checked.
This is a duplicate of bug 10926, assigned to Stephano. *** This bug has been marked as a duplicate of bug 10926 ***