memory_stress_ng test reports wrong result code
Bug #1657511 reported by
Rod Smith
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Checkbox Provider - Base |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
The memory_stress_ng script can report the wrong result code when a stressor fails -- the test reports the latest result, claiming that it's the latest FAILED result; but the latest FAILED result may have occurred several stressors before, whereas the latest result may have passed, and therefore return a "0" value.
Related branches
~rodsmith/plainbox-provider-checkbox:add-numa-testing
- Jeff Lane : Approve
-
Diff: 32 lines (+6/-1)1 file modifiedbin/memory_stress_ng (+6/-1)
| tags: | added: hwcert-server |
| summary: |
- memory_stress_ng test returns wrong result code + memory_stress_ng test reports wrong result code |
| Changed in plainbox-provider-checkbox: | |
| status: | New → Fix Committed |
| milestone: | none → 0.34.0 |
| Changed in plainbox-provider-checkbox: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
