Bug 10347

Summary: Parselog failure on nightly-rpm builder
Product: [QA/Testing] Runtime Testing Reporter: Joshua Lock <joshuagloe>
Component: generalAssignee: Saul Wold <sgw>
Status: RESOLVED WORKSFORME QA Contact: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Severity: normal    
Priority: Medium+ CC: randy.e.witt, richard.purdie
Version: 2.2   
Target Milestone: 2.2 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Joshua Lock 2016-09-29 10:30:54 UTC 
| ======================================================================
| FAIL: test_parselogs (oeqa.runtime.parselogs.ParseLogsTest)
| ----------------------------------------------------------------------
| Traceback (most recent call last):
|   File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-rpm/build/meta/lib/oeqa/utils/decorators.py", line 109, in wrapped_f
|     return func(*args, **kwargs)
|   File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-rpm/build/meta/lib/oeqa/utils/decorators.py", line 97, in wrapped_f
|     return f(*args, **kwargs)
|   File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-rpm/build/meta/lib/oeqa/runtime/parselogs.py", line 309, in test_parselogs
|     self.assertEqual(errcount, 0, msg=self.msg)
| AssertionError: 1 != 0 : Log: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-rpm/build/build/tmp/work/qemux86-poky-linux/core-image-sato/1.0-r0/dmesg_output.log
| -----------------------
| Central error: [  210.790784]  [<c18d04be>] error_code+0x5a/0x60
| ***********************
| [  210.786358]  [<c1126700>] ? trace_raw_output_mm_lru_activate+0x80/0x80
| [  210.786881]  [<c1126d25>] ? release_pages+0x225/0x290
| [  210.787282]  [<c112681b>] ? __pagevec_lru_add_fn+0x11b/0x1d0
| [  210.787757]  [<c1169cfe>] ? mem_cgroup_commit_charge+0x4e/0x390
| [  210.788237]  [<c114846c>] handle_mm_fault+0x94c/0xb50
| [  210.788666]  [<c1047552>] __do_page_fault+0x1b2/0x500
| [  210.789084]  [<c1043e30>] ? kvm_pv_reboot_notify+0x30/0x30
| [  210.789524]  [<c10478f8>] trace_do_page_fault+0x38/0xf0
| [  210.789946]  [<c1043e30>] ? kvm_pv_reboot_notify+0x30/0x30
| [  210.790384]  [<c1043e48>] do_async_page_fault+0x18/0x70
| [  210.790784]  [<c18d04be>] error_code+0x5a/0x60
| [  210.791168]  [<c1043e30>] ? kvm_pv_reboot_notify+0x30/0x30

https://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/908/steps/Running%20Sanity%20Tests/logs/stdio
Comment 1 Saul Wold 2016-10-04 22:32:41 UTC 
Still investigating this issue, setup a F23 Container using Randy's tools and currently running 500+ iterations with no failures yet.  This is being run on an Ubuntu 16.04 host so may have different behavior that running on a F23 host

I have another machine that I will setup directly with F23 Distro and I will try to run directly on that and via Containers. (my plan for tomorrow).

I also looked at LKML and did not see anything that jumped out at me as this issue.
Comment 2 Saul Wold 2016-10-06 01:07:28 UTC 
I am still working on setting up a F23 with F23 Docker (HW issues here), but will close this since I have not seen it reproduce after over 5000+ runs on my U16.04 with F23 Containers.

We can reopen if needed