diff options
| author | nirnimesh@chromium.org <nirnimesh@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-10-21 01:47:28 +0000 |
|---|---|---|
| committer | nirnimesh@chromium.org <nirnimesh@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-10-21 01:47:28 +0000 |
| commit | 4998d79f6457ca0dd9f1c74f3035a3c03f3a0b5b (patch) | |
| tree | 39e3a094176352f3fb6f019fedbe8f395739e6fc /media/tools/qt_faststart.c | |
| parent | 7de5c8e928e6f81c2283e8efb7a9e6e27db7ecf5 (diff) | |
| download | chromium_src-4998d79f6457ca0dd9f1c74f3035a3c03f3a0b5b.zip chromium_src-4998d79f6457ca0dd9f1c74f3035a3c03f3a0b5b.tar.gz chromium_src-4998d79f6457ca0dd9f1c74f3035a3c03f3a0b5b.tar.bz2 | |
Reliablity test
Introduce a flag --noclearprofile to instruct reliability test to not clear
profile before firing off the browser. This is so avoid unnecessary disk
writes. (The default value of this flag is OFF, so win reliability bot should
continue to behave as is). Mac Chromebot would fire several instances of
Chrome at a time, and I want to minimize the load it generates. I understand
that I should begin with a clean profile, so I clean-up the user-data-dir
after every few runs, rather than cleaning every single time.
BUG=25271
TEST=reliability_tests should work as is on Win
Review URL: http://codereview.chromium.org/300014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@29598 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'media/tools/qt_faststart.c')
0 files changed, 0 insertions, 0 deletions