Bug 46977 - Web Inspector: inspector/debugger-pause-on-breakpoint.html timing out on Windows
Summary: Web Inspector: inspector/debugger-pause-on-breakpoint.html timing out on Windows
Status: RESOLVED DUPLICATE of bug 45291
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Pavel Podivilov
URL: http://build.webkit.org/results/Windo...
Keywords: InRadar, LayoutTestFailure, PlatformOnly
Depends on:
Blocks:
 
Reported: 2010-10-01 05:01 PDT by Adam Roben (:aroben)
Modified: 2011-01-19 09:54 PST (History)
11 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Roben (:aroben) 2010-10-01 05:01:41 PDT 
inspector/debugger-pause-on-breakpoint.html is timing out on Windows
Comment 1 Adam Roben (:aroben) 2010-10-01 05:05:33 PDT 
<rdar://problem/8501936>
Comment 2 Pavel Podivilov 2010-10-01 05:23:33 PDT 
Looks like a problem with the bot.

http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=inspector%2Fdebugger
Comment 3 Adam Roben (:aroben) 2010-10-01 05:24:53 PDT 
(In reply to comment #2)
> Looks like a problem with the bot.
> 
> http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=inspector%2Fdebugger

I don't know how to interpret that graph. But are any of those machines running Apple's Windows port? If not, isn't it possible that a bug exists in Apple/Windows-specific code?
Comment 4 Pavel Podivilov 2010-10-01 08:42:39 PDT 
(In reply to comment #3)
> (In reply to comment #2)
> > Looks like a problem with the bot.
> > 
> > http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=inspector%2Fdebugger
> 
> I don't know how to interpret that graph. But are any of those machines running Apple's Windows port? If not, isn't it possible that a bug exists in Apple/Windows-specific code?

I don't think it's a bug, that's just a flakiness. The dashboard shows strange slowness on win debug bot, while all changes for that range look absolutely innocent. After a while, that slowness just gone, again without any reason.
Comment 5 Pavel Podivilov 2010-10-05 06:01:37 PDT 
win debug bot lag
Comment 6 Adam Roben (:aroben) 2010-10-05 06:14:40 PDT 
Closing the bug because the bot is laggy isn't the right thing to do. After all, we haven't fixed the problem!

If this is a bug in the test harness or the bot, the right thing to do is to move this bug to the Tools/Tests component (which I've now done).
Comment 7 Adam Roben (:aroben) 2010-10-05 06:17:55 PDT 
The timeout for notifyDone is 15 seconds, which is pretty long for a single test to take, even if the bot is being slow. Is there something we can do to make the test shorter? In the past we've broken up long-running tests into multiple shorter tests. Could we do that here?
Comment 8 Yury Semikhatsky 2010-10-05 06:43:35 PDT 
(In reply to comment #7)
> The timeout for notifyDone is 15 seconds, which is pretty long for a single test to take, even if the bot is being slow. Is there something we can do to make the test shorter? In the past we've broken up long-running tests into multiple shorter tests. Could we do that here?

15 seconds is definitely enough for the test. The problem must be in the test itself or in the inspector debugger tests infrastructure in general, anyways if fails quite often and we can reproduce it we should fix this.
Comment 9 Pavel Podivilov 2011-01-19 09:54:37 PST 

*** This bug has been marked as a duplicate of bug 45291 ***