memory_stress_ng needs to be more vocal for debugging

Bug #1731560 reported by Jeff Lane on 2017-11-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Provider for Plainbox - Checkbox
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.

Jeff Lane (bladernr) on 2017-11-11
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.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers