Bug 4217 - [Autobuilder] "dmesg" sanity tests failed
Summary: [Autobuilder] "dmesg" sanity tests failed
Status: RESOLVED DUPLICATE of bug 4216
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 1.4 M6
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-04-08 07:25 UTC by Bogdan Marinescu
Modified: 2013-04-08 15:23 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bogdan Marinescu 2013-04-08 07:25:31 UTC
http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-64-lsb/builds/87/steps/Running%20Sanity%20Tests/logs/stdio

| qemux86-64
| Test_Info: We can ssh on 192.168.7.4 within 0 seconds
| spawn ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@192.168.7.4 /sbin/poweroff
| Warning: Permanently added '192.168.7.4' (RSA) to the list of known hosts.
| root@192.168.7.4's password:
| Test_Info: Shutdown Test PASS
| NOTE: Test Result for qemux86-64 core-image-sato
| NOTE: Testcase PASS FAIL NORESULT
| NOTE: SSH 1 0 0
| NOTE: SCP 1 0 0
| NOTE: dmesg 0 1 0
| NOTE: smart_help 1 0 0
| NOTE: smart_query 1 0 0
| NOTE: rpm_query 1 0 0
| NOTE: connman 1 0 0
| NOTE: shutdown 1 0 0
| DEBUG: Python function do_qemuimagetest_standalone finished
| ERROR: Function failed: Some testcases fail, pls. check test result and test log!!!
ERROR: Task 1 (/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-x86-64-lsb/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.
Comment 1 Richard Purdie 2013-04-08 15:23:51 UTC
This has all the signs of being the same random segfault issue as 4217, just in a different place.

*** This bug has been marked as a duplicate of bug 4216 ***