network script should tell us what triggered a failure
Bug #1878614 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
INFO:root:Avg Transfer speed: 36708.78444444444 Mb/s
INFO:root:91.77% of theoretical max 40000 Mb/s
INFO:root:Average CPU utilization: 99.5%
WARNING:root:Poor network performance detected against 172.16.0.4
WARNING:root: CPU load: 99.5%
WARNING:root: CPU load is above 90% maximum
The first warning line should tell us explicitly (so at a glance you quickly grok) why it failed... e.g. This case should say "Network test against 172.16.0.4 failed because:" and then dump the failing data.
It's a minor issue but one I've meant to change for a while now.
Related branches
~bladernr/plainbox-provider-checkbox:1878614-modify-network-script-failure-output
- Sylvain Pineau: Approve
-
Diff: 25 lines (+5/-5)1 file modifiedbin/network (+5/-5)
| Changed in plainbox-provider-checkbox: | |
| status: | In Progress → Fix Committed |
| Changed in plainbox-provider-checkbox: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
