Most of the tests are timing out, but not all.
Should I just skip all of these tests? With this many tests failing, that seems to be the wrong thing to do ...
Adam should just fix this.
(In reply to comment #2)
> Adam should just fix this.
Yes, but we should skip the tests in the meantime while I work on it.
Added the failing tests to the skipped list in r76955
One I did not skip which I now think might also be related to this change is the fast/css/getComputedStyle/getComputedStyle-with-pseudo-element.html test, which also started failing at the same time as the other ~36 tests:
Since Adam thinks he has a fix for the other tests, I will hold off taking any action on the above test.
http://trac.webkit.org/changeset/76955 might have broken Leopard Intel Release (Tests)
Fixed in r76968.
...so I should close the bug.
http://trac.webkit.org/changeset/76968 might have broken Chromium Win Release