[Yocto-builds] buildbot failure in The Yocto Autobuilder on nightly-oecore

[Michael Halstead]

I don't know for sure if it's related or the cause but when this failure
occurred ab05 was under extreme load. The results from "ps aux" at the
shell took over 120 seconds to display. Though no services necessarily
went down our monitoring timed out. I think these timeouts are caused by
running 3 builds simultaneously.

Given the overall responsiveness of the system it's possible that the VM
was unable to start in the 50 second window allowed. Can we run this
sanity test manually to see if it will pass on a system under normal load?

Michael Halstead
Yocto Project / Sys Admin

On 04/10/2013 04:30 PM, yocto-builds at yoctoproject.org wrote:
>
>
>         Build status: FAILURE
>
> Buildslave for this Build: *ab05*
> Complete logs for all build steps:
> http://autobuilder.yoctoproject.org:8011/builders/nightly-oecore/builds/66
>
> Build Reason: Triggerable(trigger_nightly-oecore)
> Build Properties:
> *Properties(**{u'branch_trigger_bitbake_nightly-oecore': u'master',
> u'branch_trigger_meta-intel_nightly-oecore': None,
> u'repo_trigger_bitbake_nightly-oecore':
> u'git://git.openembedded.org/bitbake',
> u'commit_trigger_bitbake_nightly-oecore': u'HEAD',
> u'repo_trigger_meta-qt3_nightly-oecore':
> u'git://git.yoctoproject.org/meta-qt3',
> u'bb_trigger_meta-intel_nightly-oecore': None,
> u'commit_trigger_meta-fsl-ppc_nightly-oecore': None,
> u'bb_trigger_bitbake_nightly-oecore': u'1',
> u'repo_trigger_poky_nightly-oecore': None, 'got_revision_bitbake':
> 'c47088a86fd8ad06c1810d04d9537c4cd01e8bef', 'commit_meta-qt3':
> u'HEAD', 'revision': u'adb63ca02348af72a30cef2f20de2234b74a7200',
> u'bb_trigger_meta-qt3_nightly-oecore': u'2',
> u'commit_trigger_meta-intel_nightly-oecore': None,
> 'got_revision_meta-qt3': '4c27cce6688aa39852f3cba5e7b80ec279019605',
> u'commit_trigger_meta-fsl-arm_nightly-oecore': None,
> u'branch_trigger_meta-qt3_nightly-oecore': u'dylan',
> u'branch_trigger_eclipse-poky_nightly-oecore': None,
> u'branch_trigger_meta-fsl-arm_nightly-oecore': None,
> u'repo_trigger_eclipse-poky_nightly-oecore': None,
> 'commit-description': '1.4_M4.final-1-g4c27cce',
> u'bb_trigger_poky_nightly-oecore': None,
> u'repo_trigger_oecore_nightly-oecore':
> u'git://git.openembedded.org/openembedded-core', 'slavename': 'ab05',
> u'branch_trigger_poky_nightly-oecore': None, 'branch': u'',
> u'repo_trigger_meta-intel_nightly-oecore': None, 'repourl_oecore':
> u'git://git.openembedded.org/openembedded-core', 'distroversion':
> 'DISTRO_VERSION ??= oe-core.0',
> u'branch_trigger_meta-fsl-ppc_nightly-oecore': None,
> u'bb_trigger_meta-fsl-ppc_nightly-oecore': None,
> u'commit_trigger_meta-qt3_nightly-oecore': u'HEAD', 'workdir':
> '/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-oecore', 'repository':
> '', 'buildername': 'nightly-oecore', u'DEST':
> u'/srv/www/vhosts/autobuilder.yoctoproject.org/pub/nightly/20130410-1', 'branch_oecore':
> u'dylan', u'bb_trigger_meta-fsl-arm_nightly-oecore': None, 'codebase':
> '', u'commit_trigger_eclipse-poky_nightly-oecore': None,
> 'branch_meta-qt3': u'dylan', u'scheduler': u'trigger_nightly-oecore',
> 'got_revision_oecore': 'b7b7ebe57bd6fd248e80be0b7e517a3ceb7cfd11',
> u'bb_trigger_eclipse-poky_nightly-oecore': None,
> u'bb_trigger_oecore_nightly-oecore': u'1', 'commit_bitbake': u'HEAD',
> u'repo_trigger_meta-fsl-arm_nightly-oecore': None,
> u'commit_trigger_poky_nightly-oecore': None,
> u'repo_trigger_meta-fsl-ppc_nightly-oecore': None,
> u'branch_trigger_oecore_nightly-oecore': u'dylan', 'project': '',
> 'commit_oecore': u'HEAD', 'buildnumber': 66, 'branch_bitbake':
> u'master', u'commit_trigger_oecore_nightly-oecore': u'HEAD',
> 'repourl_bitbake': u'git://git.openembedded.org/bitbake',
> 'repourl_meta-qt3': u'git://git.yoctoproject.org/meta-qt3'})*
> /Detailed log of last build step:/
> http://autobuilder.yoctoproject.org:8011/builders/nightly-oecore/builds/66/steps/Running
> Sanity Tests/logs/stdio
> <http://autobuilder.yoctoproject.org:8011/builders/nightly-oecore/builds/66/steps/Running%20Sanity%20Tests/logs/stdio>
>
>
>
>         Last 20 lines of "Running Sanity Tests.stdio" Error log:
>
> | spawn ssh -o UserKnownHostsFile=/dev/null -o
> StrictHostKeyChecking=no root at 192.168.7.2 hostname
> | ssh: connect to host 192.168.7.2 port 22: Connection refused
> | Test_Info: We can not ssh on 192.168.7.2 in 50 seconds
> | Test_Info: Shutdown Test FAIL
> | killing 10265
> | killing 9527
> | NOTE: Test Result for qemuarm core-image-sato
> | NOTE: Testcase PASS FAIL NORESULT
> | NOTE: SSH 0 1 0
> | NOTE: SCP 0 1 0
> | NOTE: smart_help 0 1 0
> | NOTE: smart_query 0 1 0
> | NOTE: rpm_query 0 1 0
> | NOTE: connman 0 1 0
> | NOTE: dmesg 0 1 0
> | NOTE: shutdown 0 1 0
> | DEBUG: Python function do_qemuimagetest_standalone finished
> | ERROR: Function failed: Some testcases fail, pls. check test result
> and test log!!!
> ERROR: Task 0
> (/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-oecore/build/meta/recipes-sato/images/core-image-sato.bb,
> do_qemuimagetest_standalone) failed with exit code '1'
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
>
>
> *-The Yocto BuildBot*
>
>
> _______________________________________________
> Yocto-builds mailing list
> Yocto-builds at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto-builds

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto-builds/attachments/20130410/48c416cb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4516 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.yoctoproject.org/pipermail/yocto-builds/attachments/20130410/48c416cb/attachment.bin>