summaryrefslogtreecommitdiffstats
path: root/testing/scripts
diff options
context:
space:
mode:
authordpranke <dpranke@chromium.org>2016-02-12 19:45:21 -0800
committerCommit bot <commit-bot@chromium.org>2016-02-13 03:46:36 +0000
commitab24304838d16c00bdd782737d790a1d097aa8b3 (patch)
tree101468b6fe1bc855f28c5765d9b39c6b531518af /testing/scripts
parente6e2b27c63a60d3a76bdd6f7ae7cc5a7021bb318 (diff)
downloadchromium_src-ab24304838d16c00bdd782737d790a1d097aa8b3.zip
chromium_src-ab24304838d16c00bdd782737d790a1d097aa8b3.tar.gz
chromium_src-ab24304838d16c00bdd782737d790a1d097aa8b3.tar.bz2
Fix the --build-dir to the valgrind wrapper script.
Apparently the runtest.py script requires --build-dir to be the path to //out/Release (or whatever) instead of just //out (--target doesn't get added on). This patch attempts to fix that, and use an absolute path rather than a relative one, just for possible safety. TBR=bruening@chromium.org BUG=572694 NOTRY=true Review URL: https://codereview.chromium.org/1694923003 Cr-Commit-Position: refs/heads/master@{#375340}
Diffstat (limited to 'testing/scripts')
-rwxr-xr-xtesting/scripts/run_under_valgrind.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/testing/scripts/run_under_valgrind.py b/testing/scripts/run_under_valgrind.py
index 2aface1..789aa55 100755
--- a/testing/scripts/run_under_valgrind.py
+++ b/testing/scripts/run_under_valgrind.py
@@ -15,7 +15,7 @@ def main_run(args):
rc = common.run_runtest(args, [
os.path.join(common.SRC_DIR, 'tools', 'valgrind', 'chrome_tests.sh'),
'--tool', 'memcheck',
- '--build-dir', 'src/out',
+ '--build-dir', os.path.join(common.SRC_DIR, 'out', args.build_config_fs),
] + args.args)
json.dump({