summaryrefslogtreecommitdiffstats
path: root/chromeos/system
diff options
context:
space:
mode:
authorariblue <ariblue@google.com>2014-11-06 13:52:54 -0800
committerCommit bot <commit-bot@chromium.org>2014-11-06 21:53:20 +0000
commitb6bad3dc24d88ba1ce182e7ab3fbe6e2e281c998 (patch)
treec188ba94bc8b311ec5f83dd543d2406de94a562c /chromeos/system
parent66dc372e7e87901474963b5b9acd65ac854b56c3 (diff)
downloadchromium_src-b6bad3dc24d88ba1ce182e7ab3fbe6e2e281c998.zip
chromium_src-b6bad3dc24d88ba1ce182e7ab3fbe6e2e281c998.tar.gz
chromium_src-b6bad3dc24d88ba1ce182e7ab3fbe6e2e281c998.tar.bz2
In https://codereview.chromium.org/651383002/ I created a generic output
directory for all output artifacts (html/json/etc results, profiler files, etc). This reused the existing --output-dir flag used by the profile generator. The _SessionRestoreTest benchmark manually sets the output_dir in its ProcessCommandLineArgs (PCLA) function. However, here is the hierarchy of PCLA calls for run_benchmark (lower in the list happens later): - benchmark - page_runner - page_filter - results_options - benchmark_class (_SessionRestoreTest) In the results_options PCLA call, we ensure that the output_dir exists. However, in the _SessionRestoreTest PCLA call we change the output_dir (which now is guaranteed NOT to exist). This patch creates the directory we are changing to in the _SessionRestoreTest PCLA call instead. BUG=430276 Review URL: https://codereview.chromium.org/706783002 Cr-Commit-Position: refs/heads/master@{#303094}
Diffstat (limited to 'chromeos/system')
0 files changed, 0 insertions, 0 deletions