Bug 11326 - nightly-mips64 SDK sanity check failure on master-next
Summary: nightly-mips64 SDK sanity check failure on master-next
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.3 M4
Assignee: Joshua Lock
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-04-10 20:03 UTC by California Sullivan
Modified: 2017-04-12 13:36 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
SDK Sanity Tests log (35.89 KB, text/plain)
2017-04-10 20:03 UTC, California Sullivan
no flags Details
CreateAutoConf log (13.09 KB, text/plain)
2017-04-10 20:05 UTC, California Sullivan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description California Sullivan 2017-04-10 20:03:02 UTC
Created attachment 3702 [details]
SDK Sanity Tests log

core-image-sato-1.0-r0 do_testsdk: RESULTS - buildcpio.BuildCpioTest.test_cpio - Testcase -1: ERROR
core-image-sato-1.0-r0 do_testsdk: Traceback (most recent call last):
  File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-mips64/build/meta/lib/oeqa/core/case.py", line 32, in _oeSetUpClass
    clss.setUpClassMethod()
  File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-mips64/build/meta/lib/oeqa/sdk/cases/buildcpio.py", line 15, in setUpClass
    self.project.download_archive()
  File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-mips64/build/meta/lib/oeqa/sdk/utils/sdkbuildproject.py", line 24, in download_archive
    self._download_archive()
  File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-mips64/build/meta/lib/oeqa/utils/buildproject.py", line 35, in _download_archive
    subprocess.check_output(cmd, shell=True)
  File "/usr/lib64/python3.5/subprocess.py", line 316, in check_output
    **kwargs).stdout
  File "/usr/lib64/python3.5/subprocess.py", line 398, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command 'wget -O /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-mips64/build/build/tmp/work/qemumips64-poky-linux/core-image-sato/1.0-r0/testimage-sdk//cpio/cpio-2.12.tar.bz2 https://ftp.gnu.org/gnu/cpio/cpio-2.12.tar.bz2' returned non-zero exit status 4
Comment 1 California Sullivan 2017-04-10 20:05:20 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.
Comment 2 Paul Eggleton 2017-04-10 20:13:24 UTC
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/
Comment 3 Paul Eggleton 2017-04-11 02:30:53 UTC
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.
Comment 4 Joshua Lock 2017-04-12 13:36:43 UTC
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