[Webkit-unassigned] [Bug 49740] [NRWT] '--new-baseline' doesn't work

Thu Nov 18 14:07:03 PST 2010

https://bugs.webkit.org/show_bug.cgi?id=49740

--- Comment #7 from Dirk Pranke <dpranke at chromium.org>  2010-11-18 14:07:03 PST ---
(In reply to comment #6)
> As far as I remember, I ran ./WebKitTools/Scripts/test-webkit-scripts and it passed all tests.
> Could you tell me how do you guys run tests about new-run-webkit-tests?
> 

That would be sufficient. Like I said, the tests that would've caught at least part of this were disabled (and had bit-rotted accordingly). The new patch will bring them back online.

Typically I run a script I have that just runs the subset of test-webkitpy that includes the tests under layout_tests/*, and if that passes, then I'll usually run test-webkitpy to be sure nothing weird happened.

I have some other patches to test-webkitpy that should make things a little better so that I don't my separate script, and of course the patch above will allow test-webkitpy to complete in ~ 4 seconds, so that'll help, too.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.