[Webkit-unassigned] [Bug 36647] fast/loader/stateobjects/replacestate-then-pushstate.html fails intermittently on all bots

[bugzilla-daemon at webkit.org]

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


Brady Eidson <beidson at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fishd at chromium.org




--- Comment #14 from Brady Eidson <beidson at apple.com>  2010-04-02 10:13:23 PST ---
(In reply to comment #11)
> The flip side of that argument is that we have >13k tests.  Because the bots
> (Tiger and Snow Leopard especially) are constantly red, we become blind to
> failures and miss real regressions.  If we lose 0.01% of our tests, that's a
> net win for the project.

Unless the feature is new with only an initial batch of tests and disabling one
of the tests would result in the loss of ~10% of the test coverage for a
reasonably complicated mechanism.

> However, in many cases, we've been able to keep the test coverage and remove
> the flakiness, even with no access to the failures locally.  For example, last
> night I fixed a test that was failing only on Tiger with no ability to
> reproduce the failure myself.  It just requires effort.

Wildly varying amounts of effort - I have spent time on this already and no one
I've reached out to has decided it was worth helping.

(In reply to comment #12)
> > Is this one of the tests that's "failing" by showing the output from the
> > previous test?  ie - the test itself isn't necessarily failing but being
> > polluted by something prior.
> 
> Here's the failure pretty diff:
> 
> http://build.webkit.org/results/Tiger%20Intel%20Release/r57003%20(10355)/fast/loader/stateobjects/replacestate-then-pushstate-pretty-diff.html

This diff appears to be the previous test
(fast/loader/replacestate-in-iframe.html) dumping into the test that the bots
see as failing.  This appears to best a test harness problem that I would love
help tracking down, because apparently every other test I've added lately has
been affected by this problem somehow.  Any ideas?

(CC'ing Darin Fisher, who added the test that is causing the forward failure)

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