network test script needs better output

Bug #1229435 reported by Jeff Lane 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox (Legacy)
Fix Released
Medium
Jeff Lane 
Checkbox Provider - Base
Fix Released
Medium
Jeff Lane 

Bug Description

The network test script needs to provide better output to checkbox... the problem seems to be that the output from the FTP session is dumped to stdout, while the debug logging all goes to stderr.

Since checkbox is an either-or when grabbing output, this means that on a successful test, we get this:
*cmd* 'USER ubuntu'
*put* 'USER ubuntu\r\n'
*get* '331 Please specify the password.\n'
*resp* '331 Please specify the password.'
*cmd* 'PASS ******'
*put* 'PASS ******\r\n'
*get* '230 Login successful.\n'
*resp* '230 Login successful.'
*cmd* 'CWD .'
*put* 'CWD .\r\n'
*get* '250 Directory successfully changed.\n'
*resp* '250 Directory successfully changed.'
*cmd* 'TYPE I'
*put* 'TYPE I\r\n'
*get* '200 Switching to Binary mode.\n'
*resp* '200 Switching to Binary mode.'
*cmd* 'PASV'
*put* 'PASV\r\n'
*get* '227 Entering Passive Mode (172,16,5,50,124,0).\n'
*resp* '227 Entering Passive Mode (172,16,5,50,124,0).'
*cmd* 'STOR ftp_performance_test'
*put* 'STOR ftp_performance_test\r\n'
*get* '150 Ok to send data.\n'
*resp* '150 Ok to send data.'
*get* '226 Transfer complete.\n'
*resp* '226 Transfer complete.'

which doesn't inform us about the throughput speeds observed or any other data. All that logging data is only displayed if the test fails, however, it would be important to know what the throughput is even on successful tests.

Tags: scripts

Related branches

Daniel Manrique (roadmr)
tags: added: scripts
Zygmunt Krynicki (zyga)
affects: checkbox → plainbox-provider-checkbox
Zygmunt Krynicki (zyga)
Changed in plainbox-provider-checkbox:
status: New → Triaged
Revision history for this message
Jeff Lane  (bladernr) wrote :

Even since moving to iperf, there are some issues. The output on Success is ok, but the output on failure is lacking:

DEBUG:root:Shutting down interface:eth0
DEBUG:root:timeout 180 iperf -c 172.100.166.27 -n 1024M
WARNING:root:Poor network performance detected
DEBUG:root:Restoring interface:eth0

Changed in plainbox-provider-checkbox:
status: Triaged → In Progress
importance: Undecided → Medium
assignee: nobody → Jeff Lane (bladernr)
Revision history for this message
Jeff Lane  (bladernr) wrote :

Now: Console output for success:
DEBUG:root:Shutting down interface:virbr0
DEBUG:root:Shutting down interface:wlan0
DEBUG:root:timeout 180 iperf -c 192.168.0.10 -n 1024M
------------------------------------------------------------
Client connecting to 192.168.0.10, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.0.100 port 57784 connected with 192.168.0.10 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 9.2 sec 1.00 GBytes 932 Mbits/sec

Transfer speed: 932 Mb/s
93.20% of theoretical max 1000 Mb/s

DEBUG:root:Passed benchmark
DEBUG:root:Restoring interface:virbr0
DEBUG:root:Restoring interface:wlan0

Revision history for this message
Jeff Lane  (bladernr) wrote :

DEBUG:root:Shutting down interface:virbr0
DEBUG:root:Shutting down interface:wlan0
DEBUG:root:timeout 180 iperf -c 192.168.0.10 -n 1024M
WARNING:root:Poor network performance detected
WARNING:root:
Transfer speed: 94.0 Mb/s
WARNING:root:
9.40% of theoretical max 1000Mb/s

DEBUG:root:Restoring interface:virbr0
DEBUG:root:Restoring interface:wlan0

Jeff Lane  (bladernr)
Changed in checkbox-legacy:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Jeff Lane (bladernr)
Changed in checkbox-legacy:
status: In Progress → Fix Committed
Changed in plainbox-provider-checkbox:
status: In Progress → Fix Released
status: Fix Released → Fix Committed
milestone: none → 0.17
Changed in checkbox-legacy:
status: Fix Committed → Fix Released
Changed in plainbox-provider-checkbox:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.