Commit e324f0d3 authored by ojan@chromium.org's avatar ojan@chromium.org

Move the flakiness dashboard to the new instance at webkit-test-results.appspot.com

https://bugs.webkit.org/show_bug.cgi?id=114080

Reviewed by Ryosuke Niwa.

This way, the WebKit and Blink dashboard code can change as appropriate without
needing to consider the other project's needs. This still doesn't update the
buildbots to upload to the new location, or the dashboard code to pull the
results.json files from the new location, but it at least allows for changing the
UI code (e.g. the WebKit one can remove all knowledge of the Chromium bots).

* TestResultServer/app.yaml:


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@147833 268f45cc-cd09-0410-ab3c-d52691b4dbfc
parent d97b4ea1
2013-04-05 Ojan Vafai <ojan@chromium.org>
Move the flakiness dashboard to the new instance at webkit-test-results.appspot.com
https://bugs.webkit.org/show_bug.cgi?id=114080
Reviewed by Ryosuke Niwa.
This way, the WebKit and Blink dashboard code can change as appropriate without
needing to consider the other project's needs. This still doesn't update the
buildbots to upload to the new location, or the dashboard code to pull the
results.json files from the new location, but it at least allows for changing the
UI code (e.g. the WebKit one can remove all knowledge of the Chromium bots).
* TestResultServer/app.yaml:
2013-04-05 Ryosuke Niwa <rniwa@webkit.org>
Re-enable testing on the commit queue
application: test-results
application: webkit-test-results
version: 1
runtime: python
api_version: 1
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment