Sometimes, a test that causes out-of-memory conditions will trigger the OOM killer, causing the abort of the test in question plus in some cases the ones that follow (if OOM killer is still "out for blood"). This causes the bug to be filed against the wrong test case, as it happened for example with Bug 110255.
Arek/Petri, How do we proceed with this bug? Any idea, what are the next steps?
IIRC there were few things happening in this regard: Petri fine-tuning OOM from the igt_runner and Chris making the tests that stress the memory a bit less stressful.
Right now it is on people to notice similar issues and keep on tuning things until we get this under control or figure a way of getting them classified as caused by OOM killer realiably.