rebaseline_server: use new intermediate JSON format as described in https://goto...
authorcommit-bot@chromium.org <commit-bot@chromium.org@2bbb7eff-a529-9590-31e7-b0007b416f81>
Wed, 26 Feb 2014 19:05:20 +0000 (19:05 +0000)
committercommit-bot@chromium.org <commit-bot@chromium.org@2bbb7eff-a529-9590-31e7-b0007b416f81>
Wed, 26 Feb 2014 19:05:20 +0000 (19:05 +0000)
commit16f418080ff6751e15e0193263149412de9c848a
tree4704fbad68889e675a1a6c6a42723be715d8eb5e
parent1caedbb216703df58ce5ebe29955e53fa098d8dc
rebaseline_server: use new intermediate JSON format as described in https://goto.google.com/ChangingRbsJson

There are still some places in the frontend (HTML+Javascript) code where
we assume we are handling expectations vs actuals, but there are just a few
and we should be able to remove them easily in a coming CL.
At that point, the frontend will work just as well for displaying any set
of image pairs.

BUG=skia:1919
NOTRY=True
R=rmistry@google.com

Author: epoger@google.com

Review URL: https://codereview.chromium.org/178253010

git-svn-id: http://skia.googlecode.com/svn/trunk@13598 2bbb7eff-a529-9590-31e7-b0007b416f81
15 files changed:
gm/gm_json.py
gm/rebaseline_server/column.py
gm/rebaseline_server/imagediffdb.py
gm/rebaseline_server/imagepair.py
gm/rebaseline_server/imagepair_test.py
gm/rebaseline_server/imagepairset.py
gm/rebaseline_server/imagepairset_test.py
gm/rebaseline_server/results.py
gm/rebaseline_server/results_test.py
gm/rebaseline_server/server.py
gm/rebaseline_server/static/constants.js [new file with mode: 0644]
gm/rebaseline_server/static/loader.js
gm/rebaseline_server/static/view.html
gm/rebaseline_server/testdata/outputs/actual/results_test.ResultsTest.test_gm/gm.json [deleted file]
gm/rebaseline_server/testdata/outputs/expected/results_test.ResultsTest.test_gm/gm.json