network script incorrectly parsing iperf output
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox Provider - Base |
Fix Released
|
High
|
Daniel Manrique |
Bug Description
A sample run of network script on a really fast link results in this:
[ 3] local 172.100.202.227 port 39630 connected with 172.100.202.223 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 0.9 sec 1.00 GBytes 9.14 Gbits/sec
Transfer speed: 14 Gb/s
70.00% of theoretical max 20000Mb/s
Raw iperf output says 9.14 Gbits/sec, but the parsed result (the one with "Transfer Speed:" says 14 Gb/s. It's parsing the units correctly, but not the quantity, chopping off what's before the decimal point.
This is because the regex used to parse the speed won't consider a dot part of the quantity:
match = re.search(
it should be something like this:
match = re.search(
Related branches
- Zygmunt Krynicki (community): Approve
-
Diff: 46 lines (+11/-4)1 file modifiedcheckbox-old/scripts/network (+11/-4)
Changed in checkbox: | |
status: | Triaged → In Progress |
assignee: | nobody → Daniel Manrique (roadmr) |
Changed in checkbox: | |
status: | In Progress → Fix Committed |
affects: | checkbox → plainbox-provider-checkbox |
Changed in plainbox-provider-checkbox: | |
milestone: | 2014-mar-28 → none |
Changed in plainbox-provider-checkbox: | |
status: | Fix Committed → Fix Released |
milestone: | none → 0.5 |