out/gn_Debing/bin/run_chrome_junit_tests does not run tests anymore |
||||
Issue description
out/gn_Debing/bin/run_chrome_junit_tests does not run tests anymore
Instead of running JUnit tests, the command now prints
"
usage: test_runner.py [-h]
{gtest,instrumentation,junit,linker,monkey,perf,python}
"
,
Nov 21 2016
,
Nov 21 2016
The relevant part there is after what you quoted: test_runner.py: error: unrecognized arguments: --runtime-deps-path /usr/local/ssd/code/clankium/src/out-gn/Release/gen.runtime/chrome/android/chrome_junit_tests__test_runner_script.runtime_deps Fix here: https://codereview.chromium.org/2517283002/
,
Nov 21 2016
,
Nov 21 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/221b734a23bc7ae55b2104346dc34124bbe6d296 commit 221b734a23bc7ae55b2104346dc34124bbe6d296 Author: jbudorick <jbudorick@chromium.org> Date: Mon Nov 21 20:35:55 2016 [Android] Fix generated junit scripts wrt --runtime-deps-file. The junit tests don't need to worry about pushing runtime deps to the device since they don't run on the device. BUG= 667332 Review-Url: https://codereview.chromium.org/2517283002 Cr-Commit-Position: refs/heads/master@{#433631} [modify] https://crrev.com/221b734a23bc7ae55b2104346dc34124bbe6d296/build/config/android/rules.gni
,
Nov 21 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by pkotw...@chromium.org
, Nov 21 2016Status: Assigned (was: Untriaged)