Those instances are as much likely to be WebCore bugs as DRT bugs.
DRT may not be properly clearing state between tests, but it's equally
likely that WebCore is bleeding state between pages (including doing
things like smashing memory).
On Wed, Jan 19, 2011 at 3:59 AM, Osztrogonac Csaba wrote:
>
I ran into similar problem several times, it might be a DumpRenderTree
bug. One DumpRenderTree instance execute 1000 tests without restarting
by default. Sometimes it occurs that a test leaves behind some mess in
the DRT and it breaks one of the following tests. If the test passes
with "run-webkit
If this is the same as http://webkit.org/b/51807, then it's actually
been broken for a couple of weeks.
Mihai
On Tue, Jan 18, 2011 at 10:12 PM, Adam Barth wrote:
> I investigated this issue for a while. Disabling the test just causes
> the next test to fail. I'm not very familiar with this cod
I investigated this issue for a while. Disabling the test just causes
the next test to fail. I'm not very familiar with this code. I can
spend more time investigating, but having someone familiar with
ideographs would likely be more efficient.
Adam
On Tue, Jan 18, 2011 at 4:49 PM, Eric Seidel
I ran "webkit-patch failure-reason" on "Leopard Intel Release (Tests)" and got:
SUCCESS: Build 26596 (r75728) was the first to show failures:
set([u'fast/blockflow/broken-ideograph-small-caps.html'])
Suspect revisions:
r75726:
http://trac.webkit.org/changeset/75726
Bug: 52364 (https://bugs.web
5 matches
Mail list logo