| Summary: | nightly-mips64 SDK sanity check failure on master-next | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | California Sullivan <california.l.sullivan> | ||||||
| Component: | devtools / tool chain | Assignee: | Joshua Lock <joshuagloe> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | Medium+ | CC: | bluelightning, meta.mr.watcher, meta.watcher, sgw | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | 2.3 M4 | ||||||||
| Hardware: | x86 | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||||
| Attachments: |
|
||||||||
|
Description
California Sullivan
2017-04-10 20:03:02 UTC
Created attachment 3703 [details]
CreateAutoConf log
Failures in here as well:
Initialized empty Git repository in /srv/www/vhosts/autobuilder.yoctoproject.org/buildhistory/poky/master-next/nightly-mips64/.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.
That second one looks like a completely different issue. FWIW Joshua has sent a patch for the first one: https://patchwork.openembedded.org/series/6262/ Let's consider the first issue as resolved. Joshua, can you take a look into the second one? At first glance it looks like an infrastructure issue. Patch for the first issue has been merged[1]: http://git.yoctoproject.org/clean/cgit.cgi/poky/commit/?id=1b4bd1b659dca55ebe831bf1378adfc68cfb6f5f I'm working with Michael to understand why we're seeing the host key verification failure and Leo has filed bug #11334 for the fact that this failure doesn't cause the buildstep to fail: https://bugzilla.yoctoproject.org/show_bug.cgi?id=11334 |