Bug 93134 - [NRWT] Rename to not have "new" anywhere
Summary: [NRWT] Rename to not have "new" anywhere
Status: RESOLVED DUPLICATE of bug 126580
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: NRWT
Depends on:
Blocks:
 
Reported: 2012-08-03 09:58 PDT by Alexey Proskuryakov
Modified: 2014-02-06 08:02 PST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Proskuryakov 2012-08-03 09:58:14 PDT
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.
Comment 1 Dirk Pranke 2012-08-03 10:50:33 PDT
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.
Comment 2 Csaba Osztrogonác 2012-08-04 22:41:33 PDT
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.
Comment 3 Csaba Osztrogonác 2014-02-06 08:02:59 PST

*** This bug has been marked as a duplicate of bug 126580 ***