Rebuild test history databases when starting up performance_ui_tests.
[In this reland, manually load the browser dll as a resource on Windows.]
Previously, whenever the theme or history database format were modified, a
large binary database or pak file had to be committed. This was only done
intermittently, messing up some perf expectations. Since last June, this
has added over 100 megabytes to our repository weight.
By generating the SQLite databases and Cached Theme.pak files at startup
of the one test suite that uses them, we're guaranteed that we'll always
be using the current versions and won't add upgrade costs to our
performance_ui_tests. We'll also not continuously add to new binary
resources to the permanent git archive.
BUG=111570
TBR=sky@chromium.org
First Review: https://codereview.chromium.org/14273023
Review URL: https://codereview.chromium.org/14585015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@200094 0039d316-1c4b-4281-b951-d872f2087c98
41 files changed
