Bug #7562
closed
Intermittent sigkill on mysql tests during ReportTest
Description
example: http://ci.theforeman.org/job/test_develop_pr_core/2365/database=mysql,puppet=3.0,ruby=1.8.7/console
`ReportTest#test_0011_should expire reports created 1 week ago = rake aborted!
SIGKILL`
Updated by Dominic Cleal about 9 years ago
I'm not really sure that this test is particularly memory-intensive, surely this is just an infrastructure issue rather than something in the test?
Killed process 23444, UID 501, (ruby) total-vm:1999508kB, anon-rss:550892kB, file-rss:1276kBis the OOM message.
Updated by Ori Rabin about 9 years ago
It keeps happening after this test and the test creates 50 reports so it could help to reduce the number of reports created
I'm not sure if this is the only problem but I've seen this a couple of times since the test was merged
Updated by Dominic Cleal about 9 years ago
I think you're right, it probably is this test. Maybe each report contains a lot of messages too?
I notice the time taken is quite long:
ReportTest#test_0011_should expire reports created 1 week ago = 15.72 s = .
And although I've increased swap on our slaves to avoid it, I notice most remaining SIGKILLs are in the vicinity of this test.
Updated by The Foreman Bot about 9 years ago
- Status changed from Assigned to Ready For Testing
- Target version set to 1.7.2
- Pull request https://github.com/theforeman/foreman/pull/1855 added
- Pull request deleted (
)
Updated by Ori Rabin about 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset bd058e6739a0020e35056d7c223f7dfe16eec785.
Updated by Dominic Cleal about 9 years ago
- translation missing: en.field_release set to 21