Would it be worth getting a buildbot going with these? I find it's useful for one simple reason: you can look at the buildbot output to find which tests are still broken. That way you don't need to keep a spreadsheet (or whatever) up-to-date with remaining work.
On Thu, Oct 9, 2008 at 7:33 AM, Mike Pinkerton <[EMAIL PROTECTED]> wrote: > > This morning, I landed support in the layout test harness for Mac, > which means we can start running the layout tests. Even though we're > showing sea-green to the user, we can still get the render tree and > verify that JS/v8 is working correctly behind the scenes. > > For info about how to run the tests, look at: > > > http://sites.google.com/a/chromium.org/dev/developers/testing/webkit-layout-tests > > I usually run them with: > > $ webkit/tools/layout_tests/run_webkit_tests_mac.sh --debug --verbose > > The logs go into webkit/Debug/layout_test_results so you can see > what's passing and failing. Right now, we fail a bunch because our > networking layer has some "not implemented" output (proxies, etc) that > works its way into the diff and causes failure. We also get some hangs > with timeouts and crashes in webcore. It's a start at least! > > -- > Mike Pinkerton > Mac Weenie > [EMAIL PROTECTED] > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
