[Webkit-unassigned] [Bug 105619] New: Remove old-run-webkit-tests support from webkitpy
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Dec 20 23:07:38 PST 2012
https://bugs.webkit.org/show_bug.cgi?id=105619
Summary: Remove old-run-webkit-tests support from webkitpy
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Tools / Tests
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: eric at webkit.org
CC: abarth at webkit.org, dpranke at chromium.org,
lforschler at apple.com
Remove old-run-webkit-tests support from webkitpy
It's just confusing things. Only Apple Win still uses old-run-webkit-tests, and the Apple-Win EWS does not run tests.
I believe partially-broken NRWT support is at the root of bug 103839, in part because NRWT is currently a second-class "experimental" citizen in the EWS code. Since NRWT has now long been the default, we should make it a real boy and kill ORWT (since I'm very likely to break it by re-working this code anyway).
At least the following tools will break:
1. sheriff-bot, webkit-patch will no longer understand ORWT results files (from Apple-Win buildbots, etc.)
2. webkit-patch build-and-test (something no one uses) will not work on AppleWin
3. The AppleWin EWS cannot graduate to a testing-EWS w/o moving to NRWT (that's probably for the best, given how impossibly slow it is already).
There is no urgency to this, but again, I think it's likely I may break ORWT support in webkitpy by accident as part of fixing bug 103839.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list