Bug 445905
Summary: | CORE and MEMORY fail when run from hts on RHEL 5.1 FV 32-bit Guest | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | David Aquilina <dwa> | ||||
Component: | Test Suite (harness) | Assignee: | Greg Nichols <gnichols> | ||||
Status: | CLOSED NOTABUG | QA Contact: | |||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 5 | CC: | flanagan, tao | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2008-05-28 14:52:44 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
David Aquilina
2008-05-09 18:37:41 UTC
output.log from core test: Running ./CORE2: Checking clock jitter ... Single CPU detected. No clock jitter testing necessary. clock direction test: start time 1207927725, stop time 1207927785, sleeptime 60, delta 0 PASSED stress: FAIL: [29038] (416) <-- worker 29065 got signal 11 stress: WARN: [29038] (418) now reaping child worker processes stress: FAIL: [29038] (422) kill error: No such process stress: FAIL: [29038] (416) <-- worker 29059 got signal 11 stress: WARN: [29038] (418) now reaping child worker processes stress: FAIL: [29038] (422) kill error: No such process stress: FAIL: [29038] (416) <-- worker 29056 got signal 11 stress: WARN: [29038] (418) now reaping child worker processes stress: FAIL: [29038] (422) kill error: No such process stress: FAIL: [29038] (416) <-- worker 29047 got signal 11 stress: WARN: [29038] (418) now reaping child worker processes stress: FAIL: [29038] (422) kill error: No such process stress: FAIL: [29038] (416) <-- worker 29050 got signal 11 stress: WARN: [29038] (418) now reaping child worker processes stress: FAIL: [29038] (422) kill error: No such process stress: FAIL: [29038] (416) <-- worker 29053 got signal 11 stress: WARN: [29038] (418) now reaping child worker processes stress: FAIL: [29038] (422) kill error: No such process stress: FAIL: [29038] (416) <-- worker 29041 got signal 11 stress: WARN: [29038] (418) now reaping child worker processes stress: FAIL: [29038] (422) kill error: No such process stress: FAIL: [29038] (416) <-- worker 29062 got signal 11 stress: WARN: [29038] (418) now reaping child worker processes stress: FAIL: [29038] (422) kill error: No such process stress: FAIL: [29038] (416) <-- worker 29071 got signal 11 stress: WARN: [29038] (418) now reaping child worker processes stress: FAIL: [29038] (422) kill error: No such process stress: FAIL: [29038] (416) <-- worker 29068 got signal 11 stress: WARN: [29038] (418) now reaping child worker processes stress: FAIL: [29038] (422) kill error: No such process stress: FAIL: [29038] (416) <-- worker 29074 got signal 11 stress: WARN: [29038] (418) now reaping child worker processes stress: FAIL: [29038] (422) kill error: No such process stress: FAIL: [29038] (416) <-- worker 29044 got signal 11 stress: WARN: [29038] (418) now reaping child worker processes stress: FAIL: [29038] (422) kill error: No such process stress: FAIL: [29038] (452) failed run completed in 600s stress: info: [29038] dispatching hogs: 12 cpu, 12 io, 12 vm, 0 hdd Error: stress returned failure (12) ...finished running ./CORE2, exit code=12 Created attachment 304975 [details]
System log from when the test ran and failed
random comments... sig11 is a memory failure of some sort be it exhaustion or otherwise. Looking @ the test system, it looks as though without the proper level of swap (1.2GB RAM w/300MB swap looks less than idea) then the memory test will get OOM'd. The core test however looks a bit trickier and adding swap does not resolve. Closing as system configuration issue. |