memory_stress_ng needs to be more vocal for debugging
Bug #1731560 reported by
Jeff Lane
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Checkbox Provider - Base |
Fix Released
|
Medium
|
Jeff Lane | ||
Bug Description
while trying to debug OOMKiller issues with the memory_stress_ng test I realized we should be a bit more vocal about what is being done at the moment. We need to add just a bit of instrumentation to syslog to correspond with any call traces or OOMKiller invocations that appear so we'll quickly know what triggered the problem.
Related branches
~bladernr/plainbox-provider-checkbox:1731560-vocal-memory-stress
- Paul Larson: Approve
-
Diff: 12 lines (+1/-0)1 file modifiedbin/memory_stress_ng (+1/-0)
| Changed in plainbox-provider-checkbox: | |
| status: | In Progress → Fix Committed |
| Changed in plainbox-provider-checkbox: | |
| status: | Fix Committed → Fix Released |
| status: | Fix Released → Fix Committed |
| milestone: | 0.41.0 → 0.42.0 |
| Changed in plainbox-provider-checkbox: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
