Bug 93134
| Summary: | [NRWT] Rename to not have "new" anywhere | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | dpranke, eric, jberlin, lforschler, mjs, ossy |
| Priority: | P2 | Keywords: | NRWT |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Alexey Proskuryakov
Calling something "new" is not a good practice - new things don't remain new for long.
Now that NRWT is the default, "new" in the name is also misleading, making one think that this is some kind of experiment.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Dirk Pranke
any objection to changing the buildbot configs to invoke ORWT directly on the apple win bots? I think some large part of the reason we haven't renamed NRWT yet is because we still have the run-webkit-tests wrapper that decides which script to call. Until we can get rid of that I don't really want to rename things.
Csaba Osztrogonác
To change master.cfg to call NRWT directly, we should pass --child-processes=1
to the Qt bots as the run-webkit-tests wrapper does now.
Csaba Osztrogonác
*** This bug has been marked as a duplicate of bug 126580 ***