network_bandwidth_test log option doesn't write log unless --log-level=debug is also specified

Bug #1036782 reported by Jeff Lane 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox Provider - Base
Fix Released
Low
Unassigned

Bug Description

When running network_bandwidth_test, there are two log related options.

--log sets a log file to output results to
--log-level sets the logging level

however, when using --log, logging info, including INFO level messages are ONLY written to the specified log file when --log-level is also set to debug.

So this should be changed to where --log implies DEBUG level output, or fixed so that the appropriate messages are actually written to the log file when the script runs.

Revision history for this message
Daniel Manrique (roadmr) wrote :

Steps to reproduce:

- From the checkbox trunk run:
sudo PYTHONPATH=. scripts/network_bandwidth_test --log=/tmp/something

Expected result: Something in the logfile
Actual result: Nothing in the logfile

Setting to Triaged, work to do: make it so that, if --log is specified, log-level defaults to something useful.e

Changed in checkbox:
status: New → Triaged
importance: Undecided → Low
Zygmunt Krynicki (zyga)
affects: checkbox → plainbox-provider-checkbox
Revision history for this message
Maciej Kisielewski (kissiel) wrote :

This script got removed by Sylvain in commit 18f79d91e4376193287b980c60452b9a6696d221 on Jul 3rd 2017.

And I consider the removal to be the ultimate fix!

Changed in plainbox-provider-checkbox:
status: Triaged → 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.