RESOLVED FIXED 205821
Test history links on the dashboard should go to the new results database
https://bugs.webkit.org/show_bug.cgi?id=205821
Summary Test history links on the dashboard should go to the new results database
Ryan Haddad
Reported 2020-01-06 11:38:49 PST
Test history links on the dashboard should go to the new results database (results.webkit.org). They currently point to the old one (webkit-test-results.webkit.org). Steps to reproduce: 1. Open https://build.webkit.org/dashboard/ 2. Hover over a bubble with layout test failures 3. Click the history link next to a test name 4. Observe that the results are displayed on webkit-test-results.webkit.org instead of the new results.webkit.org
Attachments
Patch (5.35 KB, patch)
2020-01-21 13:28 PST, Matt Lewis
jbedard: review+
Radar WebKit Bug Importer
Comment 1 2020-01-06 11:39:37 PST
Matt Lewis
Comment 2 2020-01-21 13:28:50 PST
Matt Lewis
Comment 3 2020-01-21 13:31:25 PST
There are a bunch of unittest failures but they are from existing failures, I'm working on a patch to help fix those in a separate bug: https://bugs.webkit.org/show_bug.cgi?id=206548
Aakash Jain
Comment 4 2020-01-21 13:33:50 PST
Comment on attachment 388341 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=388341&action=review Can you provide an example of before and after url for test failure? > Tools/BuildSlaveSupport/build.webkit.org-config/public_html/TestFailures/scripts/ui.js:50 > + return 'https://results.webkit.org/?suite=layout-tests&test=' + encodeURIComponent(testsParameter); Do we need the '/' in 'results.webkit.org/'?
Matt Lewis
Comment 5 2020-01-21 13:43:34 PST
Jonathan Bedard
Comment 6 2020-01-21 14:48:29 PST
Comment on attachment 388341 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=388341&action=review >> Tools/BuildSlaveSupport/build.webkit.org-config/public_html/TestFailures/scripts/ui.js:50 >> + return 'https://results.webkit.org/?suite=layout-tests&test=' + encodeURIComponent(testsParameter); > > Do we need the '/' in 'results.webkit.org/'? It it pedantically correct, but we don't need it.
Matt Lewis
Comment 7 2020-01-22 08:59:36 PST
Note You need to log in before you can comment on or make changes to this bug.