Code Review / yardstick.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 2aa1cd3) | patch
Remove setting logger level to debug in scenarios 19/1619/1
authorKristian Hunt <kristian.hunt@gmail.com>
Wed, 16 Sep 2015 08:34:33 +0000 (10:34 +0200)
committerKristian Hunt <kristian.hunt@gmail.com>
Wed, 16 Sep 2015 09:08:24 +0000 (11:08 +0200)
commitd53407ddf0c43bdc79f15a8fe67333090613f90a
treea7859e9efb05712bf686738354a0e92a20aba29dtree | snapshot
parent2aa1cd3922f26b9d8c9bdad310463caa5eeb8136commit | diff
Remove setting logger level to debug in scenarios

Logging level should be specified using a command line flag -v or -d
when running yardstick, rather than hardcoded into source code. If the
message is to be displayed whenever yardstick is executed regardless
of the verbosity level, then the message should be logged to warning
or error levels, instead of debug.

JIRA: YARDSTICK-95

Change-Id: Idc9b81b583f4999bfbc57893f0ab3c3675c70f71
Signed-off-by: Kristian Hunt <kristian.hunt@gmail.com>
yardstick/benchmark/scenarios/compute/lmbench.py diff | blob | history
yardstick/benchmark/scenarios/compute/perf.py diff | blob | history
yardstick/benchmark/scenarios/networking/iperf3.py diff | blob | history
yardstick/benchmark/scenarios/networking/ping.py diff | blob | history
yardstick/benchmark/scenarios/networking/pktgen.py diff | blob | history
yardstick/benchmark/scenarios/storage/fio.py diff | blob | history