[Webkit-unassigned] [Bug 16853] http/tests/loading has different results when run with run-webkit-tests -1

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=16853





------- Comment #11 from freyther at handhelds.org  2008-01-13 16:23 PDT -------
(In reply to comment #10)
> Please do check the referenced patch - it's basically the same problem.
> Something in a test was changing DRT state in a way that affected following
> tests. We've seen similar problems (not always related to loading) many times
> before, there's really not much special about FrameLoaderClient callbacks that
> warrants changing tracks now.
> 
> Of course, always running the whole test suite with -1 is not an option.
> 

Again my short term goal is to get bug #15765 fixed and this bug is blocking
it.

We have two options (at least):
   - Change the title and make it a general (e.g. "run-webkit-tests -1 gives
other results than run-webkit-tests"). This means bug #15765 will not be fixed
any time soon.

   - Run "run-webkit-tests -1" and try to find classes of failures, e.g.
dumpFrameLoadCallbacks would be one class and file one bug report for each
class as "run-webkit-tests -1" is not an option (with having one meta bug).

Sure we have to keep the big picture of DRT and run-webkit-tests interaction in
mind but I think instead of hand waving and questioning the whole interaction
let us fix the issues case by case. This would be done case by case.


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