You can just run the tests as indicated in the stdio of the failing buildbot.
On Wed, Nov 6, 2013 at 7:30 PM, Nebojša Ćirić <[email protected]> wrote: > I am not sure how it broke the WebKit tests. All the failures were about > added parameters of arguments and caller, like so: > > FAIL getSortedOwnPropertyNames(Boolean) should be length,name,prototype. Was > arguments,caller,length,name,prototype. > > Our CL didn't touch that AFAIK. > > All other tests are passing (intl, mjsunit, ...) > > What's the best way to run WebKit tests? Checkout Chromium, replace V8 and > run? > > > > 2013/11/6 <[email protected]> > > Got reverted in https://chromiumcodereview.appspot.com/62563002/ due to >> test >> failures. >> >> https://codereview.chromium.org/60013010/ >> > > > > -- > Nebojša Ćirić > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
