aboutsummaryrefslogtreecommitdiff
path: root/crosperf/schedv2.py
diff options
context:
space:
mode:
authorLuis Lozano <llozano@chromium.org>2015-12-10 10:47:01 -0800
committerchrome-bot <chrome-bot@chromium.org>2015-12-15 01:21:49 +0000
commit036c9233742004aa773a374df381b1cf137484f5 (patch)
treeb1566971ae12ed6ec13f086dd450eca741604f26 /crosperf/schedv2.py
parente627fd61c2edba668eb2af8221892286b13f05a3 (diff)
downloadtoolchain-utils-036c9233742004aa773a374df381b1cf137484f5.tar.gz
crosperf: RunCommand should return one type of object.
Cleaned up the interfaces for the RunCommand routines. These were returning different types (int or tuple) depending on the value of the return_ouput parameter. Returning different unrelated types from a routine is bad practice. Linter complains about this with several warnings like this: "Attempting to unpack a non-sequence defined at line XY of utils.command_executer" BUG=chromium:566256 TEST=ran crosperf with a example experiment file Ran run_tests. Change-Id: Ibb83ab9322c87558077fc4937ef5c0686bbe5417 Reviewed-on: https://chrome-internal-review.googlesource.com/241459 Commit-Ready: Luis Lozano <llozano@chromium.org> Tested-by: Luis Lozano <llozano@chromium.org> Reviewed-by: Han Shen <shenhan@google.com>
Diffstat (limited to 'crosperf/schedv2.py')
-rw-r--r--crosperf/schedv2.py3
1 files changed, 1 insertions, 2 deletions
diff --git a/crosperf/schedv2.py b/crosperf/schedv2.py
index 46d5657b..b73d384f 100644
--- a/crosperf/schedv2.py
+++ b/crosperf/schedv2.py
@@ -152,9 +152,8 @@ class DutWorker(Thread):
checksum_file = "/usr/local/osimage_checksum_file"
try:
rv, checksum, _ = command_executer.GetCommandExecuter().\
- CrosRunCommand(
+ CrosRunCommandWOutput(
"cat " + checksum_file,
- return_output=True,
chromeos_root=self._sched._labels[0].chromeos_root,
machine=self._dut.name,
print_to_console=False)