diff options
| author |  epoger <epoger@google.com> | 2014-07-09 07:59:06 -0700 |
|---|---|---|
| committer |  Commit bot <commit-bot@chromium.org> | 2014-07-09 07:59:06 -0700 |
| commit | 6132b436d8723beaf06d1a8a0880f4f1535908a0 (patch) | |
| tree | 3e69cfc7530c9b3450da437ea0d0e0be5e169b2c /tools | |
| parent | bd7746da97e389c1068333117407b213b378f9db (diff) | |
rebaseline_server: cache results in long-running ImageDiffDB instance
Rather than rebuilding the ImageDiffDB from scratch every time we update expected/actual results, keep the same ImageDiffDB instance around and add image pairs to it.
This makes updating results within a long-running server.py *much* faster, and tests out an idea I'm ruminating in https://goto.google.com/LongRunningImageDiffDBServer : we could run an ImageDiffDB server that developers could connect to from their locally running rebaseline_server instances, for much faster launch times.
BUG=skia:2414
NOTRY=True
R=rmistry@google.com
Author: epoger@google.com
Review URL: https://codereview.chromium.org/379563005
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions