I would recommend all ports who haven't switched to ORWT do so. NRWT is currently a white-list, see: http://trac.webkit.org/browser/trunk/Tools/Scripts/run-webkit-tests#L66
but soon it will be a black-list, or no list at all. Ports should use NRWT. If any port is having trouble, I'm *happy* to help fix things. :) -eric On Fri, Oct 21, 2011 at 12:52 PM, Antonio Gomes <toniki...@gmail.com> wrote: > Hi Eric. > > So does it it mean that any "being upstream'ed" port which was also > providing a ORWT based bot, should actually switch to NRWT instead? > > Cheers, > > On Thu, Oct 20, 2011 at 12:59 AM, Eric Seidel <e...@webkit.org> wrote: >> >> After a long hiatus, I'm back working on NRWT. >> >> As of this evening all of the blocking issues to switching the WK2 bot >> are resolved: >> https://bugs.webkit.org/show_bug.cgi?id=56729 >> >> Just waiting for the WK2 bot to have some smaller number of failures, >> then I'll pull the trigger. >> >> >> After WK2 is switched to NRWT, there is only --leaks and Windows to >> switch, before we can consider deleting ORWT. >> >> Interested parties can continue to track the NRWT migration here: >> https://bugs.webkit.org/show_bug.cgi?id=34984 >> >> -eric >> _______________________________________________ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > > > -- > --Antonio Gomes > _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev