[networking/bandwidth] script run error

[Samantha Jian-Pielak]

checkbox 0.13.4~ppa0.12.04 and checkbox-certification 0.13.1~ppa20.12.04 on Precise Beta amd64.

run network_bandwidth_test --log-level=info --scan=3 in /usr/share/checkbox/scripts/
[sudo] password for u:
Traceback (most recent call last):
  File "./network_bandwidth_test", line 678, in <module>
    sys.exit(main())
  File "./network_bandwidth_test", line 671, in main
    if not application.run():
  File "./network_bandwidth_test", line 577, in run
    if not self.test_interface(interface, targets):
  File "./network_bandwidth_test", line 529, in test_interface
    logging.debug("Testing %s/%s-Mbps", interface.name, interface.speed)
  File "./network_bandwidth_test", line 151, in speed
    return speed / 1024 / 1024
TypeError: unsupported operand type(s) for /: 'str' and 'int'

[Jeff Lane  (bladernr)]

I've seen this before myself, so confirming this and targeting it to Precise

[Jeff Lane  (bladernr)]

Can you reproduce this but use "-l network_bandwidth.log --log-level=debug" and see if that produces anything useful?

Also, what kind of system is this? And what kind of network devices does it have? Are they connected prior to you running this test?

I've tried on a Precise system here, using the script from trunk and can not get the traceback you're getting.

Also, can you provide the output of ethtool for the ethernet device on that machine?

[Daniel Manrique (roadmr)]

OK, we observed this on a system when testing the wireless network (would it be possible to confirm that this happened on wireless *only* from all reporters?). This happens because iwconfig can now return a float, whereas the code only handled integers, look at this sample output:

wlan0 IEEE 802.11bgn ESSID:"IROCK"
          Mode:Managed Frequency:2.437 GHz Access Point: 00:1E:13:6D:56:20
          Bit Rate=54 Mb/s Tx-Power=19 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=56/70 Signal level=-54 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:57 Missed beacon:0

The "Bit Rate" line is used to determine max theoretical bandwidth. But on some systems it can return:

Bit Rate = 72.2 Mb/s

This was throwing the parser off.

A fix will be available in a short while (by cr3, not by me; I'm just babbling here).