46977 2010-10-01 05:01:41 -0700 Web Inspector: inspector/debugger-pause-on-breakpoint.html timing out on Windows 2011-01-19 09:54:37 -0800 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) All All RESOLVED DUPLICATE 45291 http://build.webkit.org/results/Windows%20Debug%20(Tests)/r68872%20(20569)/results.html InRadar, LayoutTestFailure, PlatformOnly P2 Normal --- 1 aroben podivilov apavlov bweinstein joepeck keishi loislo pfeldman pmuellr podivilov rik timothy yurys oldest_to_newest 288175 0 aroben 2010-10-01 05:01:41 -0700 inspector/debugger-pause-on-breakpoint.html is timing out on Windows 288182 1 aroben 2010-10-01 05:05:33 -0700 <rdar://problem/8501936> 288186 2 podivilov 2010-10-01 05:23:33 -0700 Looks like a problem with the bot. http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=inspector%2Fdebugger 288187 3 aroben 2010-10-01 05:24:53 -0700 (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? 288262 4 podivilov 2010-10-01 08:42:39 -0700 (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. 289549 5 podivilov 2010-10-05 06:01:37 -0700 win debug bot lag 289552 6 aroben 2010-10-05 06:14:40 -0700 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). 289554 7 aroben 2010-10-05 06:17:55 -0700 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? 289568 8 yurys 2010-10-05 06:43:35 -0700 (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. 336589 9 podivilov 2011-01-19 09:54:37 -0800 *** This bug has been marked as a duplicate of bug 45291 ***