Open
Bug 938682
Opened 12 years ago
Updated 3 years ago
Eagerly report OOM to stderr when running tests
Categories
(Core :: Memory Allocator, enhancement)
Core
Memory Allocator
Tracking
()
NEW
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: sheriffing-untriaged)
It can be hard to tell whether a test failure was due to running out of memory. OOMing should be reported to stderr.
Furthermore, tests that unexpectedly OOM should turn the tree orange regardless of whether the exact OOM that happens to be hit causes the test to fail by its own logic.
(cf bug 937550 for JS fuzzing)
| Reporter | ||
Updated•12 years ago
|
Keywords: sheriffing-untriaged
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•