37259 2010-04-08 02:05:24 -0700 fast/dom/SelectorAPI/dumpNodeList tests fail when run out of order 2010-04-08 02:51:24 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) PC OS X 10.5 NEW P2 Normal --- 1 eric webkit-unassigned abarth mitz sam oldest_to_newest 210092 0 eric 2010-04-08 02:05:24 -0700 fast/dom/SelectorAPI/dumpNodeList tests fail when run out of order fast/dom/SelectorAPI/dumpNodeList-almost-strict.html fast/dom/SelectorAPI/dumpNodeList.html For whatever reason "dump" is not always defined on the value returned from querySelectorAll. It's possible that bad prototypes are bleeding through from a previous test? Or that querySelectorAll is returning something other than an Element or a NodeList? One easy way to fix this test would be to use functions which check instanceof instead of bothering with modifying the prototypes. That way we could ASSERT in the case of objects we don't understand. Also, we could simply check for the existance of "dump" before calling it, and print some debugging message if it's not there. 210093 1 eric 2010-04-08 02:06:02 -0700 This was noticed while running new-run-webkit-tests which does not guarantee test order as it will run tests in parallel (by directory). 210105 2 eric 2010-04-08 02:50:54 -0700 Committed r57268: <http://trac.webkit.org/changeset/57268> 210106 3 eric 2010-04-08 02:51:24 -0700 The above commit was to update test_expectations.txt to note these tests as flaky until this bug can be fixed.