Arrow waits for 3-4 mins after timeout due to page load and before retrying

[pranavparikh]

From logs

014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396]Capabilities [{platform=XP, databaseEnabled=true, cssSelectorsEnabled=true, javascriptEnabled=true, acceptSslCerts=true, handlesAlerts=true, browserName=firefox, browserConnectionEnabled=true, nativeEvents=true, webStorageEnabled=true, rotatable=false, locationContextEnabled=true, applicationCacheEnabled=true, takesScreenshot=true, version=25.0}] 2014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396][36m[2014-03-04 10:40:02.786] [DEBUG] TestSession - [39mError while running controller :Error in getting url - http://en-us.qe.qa1p.global.media.yahoo.com/news/hnews-ap-test.html?_product_version=classic : ScriptTimeoutError: Timed out waiting for page load. 2014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396]Command duration or timeout: 60.01 seconds 2014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396]Build info: version: '2.37.0', revision: 'a7c61cb', time: '2013-10-18 17:14:00' 2014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396]System info: host: 'Config2021VM32', ip: '10.73.137.207', os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version: '1.7.0_40' 2014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396]Session ID: 6df353a1-e13b-40a1-ad29-302b458f70be 2014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396]Driver info: org.openqa.selenium.firefox.FirefoxDriver 2014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396]Capabilities [{platform=XP, databaseEnabled=true, cssSelectorsEnabled=true, javascriptEnabled=true, acceptSslCerts=true, handlesAlerts=true, browserName=firefox, browserConnectionEnabled=true, nativeEvents=true, webStorageEnabled=true, rotatable=false, locationContextEnabled=true, applicationCacheEnabled=true, takesScreenshot=true, version=25.0}] 2014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396][32m[2014-03-04 10:40:02.786] [INFO] TestSession - [39m 2014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396]Please find the artifacts for the failed test - Hnews -
2014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396]Screenshot: tests/arrow/node/arrow-target/screenshots/func/MediaArticleBody-descriptor.json/arrow-2.png 2014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396] 2014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396]HTML: /tests/arrow/node/arrow-target/screenshots/func/MediaArticleBody-descriptor.json/arrow-2.html 2014/03/04 10:40:02 [PID:14138]2014/03/04 10:40:02 [PID:14396] 2014/03/04 10:44:47 [PID:14138]2014/03/04 10:44:47 [PID:14396][32m[2014-03-04 10:44:47.789] [INFO] TestSession - [39m 2014/03/04 10:44:47 [PID:14138]2014/03/04 10:44:47 [PID:14396]Retrying Test, Attempt #2

The screenshots were created at 10:40 and the retry started at 10:44.

In testSession class,

self.recordFailure(self.retryCount, function() {
            self.driver.stop(function() {
                self.logger.info("\nRetrying Test, Attempt #" +

self.retryCount); self.runTest(callback); }); });

Something in driver.stop() might be causing the bottleneck.