Has the issue with run-webkit-tests putting pixel tests in cross-platform directories instead of platform-specific directories been fixed? That was the showstopper for me.
dave ([email protected]) On Oct 27, 2011, at 5:00 PM, Eric Seidel wrote: > As of this afternoon, the Apple-Win bot is the only remaining buildbot > (to my knowledge) using old-run-webkit-tests > (https://bugs.webkit.org/show_bug.cgi?id=38756). > > Unfortunately, that's not likely to change soon. But all other > platforms (and all other developers) besides Apple-Win should be using > new-run-webkit-tests (it's automatically called for you when you run > run-webkit-tests). > > If you're still using old-run-webkit-tests for your work, I would > *love* to know and fix any issues you may have with NRWT. > > > In the next week I'll be moving run-webkit-tests from using a > white-list of NRWT-supported ports, to a black-list. Meaning any > private (or future) ports which may not be using NRWT yet will need to > switch, or we'll need to add a special exception in run-webkit-tests > for that port. > > Thank you for your patience in this process. I've started to burn > down the list of polish bugs > (https://bugs.webkit.org/show_bug.cgi?id=64491) and plan to close the > "switch all bots" bug (https://bugs.webkit.org/show_bug.cgi?id=34984) > once we move run-webkit-tests from whitelisting NRWT supported ports > to blacklisting ports which still require ORWT. > > -eric > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
