Last modified: 2014-06-02 22:02:43 UTC
This seems to be happening somewhat regularly with Visual Editor jobs run in the "Linux Firefox" environment via CloudBees SauceLabs: https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/203/testReport/(root)/VisualEditor%20Indent,%20Outdent/check_indent_and_outdent_enable_and_disable__outline_example_____Bullets___enabled___disabled___/ Error message reported from SauceLabs is: unexpected response, code=404, content-type="text/plain" ERROR Job 68d1926e89f24b24a35272766e190eb5 is not in progress. It may have recently finished, or experienced an error. You can learn more at https://saucelabs.com/jobs/68d1926e89f24b24a35272766e190eb5 (Selenium::WebDriver::Error::WebDriverError) ./features/step_definitions/bullets_steps.rb:34:in `/^I click Bullets$/' features/indent_outdent.feature:11:in `When I click <control>' Looking at the Selenium log captured via SauceLabs, we may discover: [22.744][FINER]: Waiting for all views to stop loading... 559[22.745][FINER]: Done waiting for all views to stop loading 560[23.567][FINER]: Waiting for all views to stop loading... 561[23.625][FINER]: Done waiting for all views to stop loading 562[23.625][WARNING]: AfterExecuteCommand failed: Chrome did not respond to 'WaitForAllTabsToStopLoading'. Elapsed time was 57 ms. 563[23.625][FINE]: Command finished (/session/78a6e87ee7f7d38f694da3813857645f/url) with response { 564 "sessionId": "78a6e87ee7f7d38f694da3813857645f", 565 "status": 0, 566 "value": { 567 568 } 569} The same test runs without errors on a local Linux machine with Firefox. From the Selenium log on SauceLabs, we discover the following configuration info: 43[3.622][FINE]: Command received (/session/78a6e87ee7f7d38f694da3813857645f) 44[3.622][FINE]: Command finished (/session/78a6e87ee7f7d38f694da3813857645f) with response { 45 "sessionId": "78a6e87ee7f7d38f694da3813857645f", 46 "status": 0, 47 "value": { 48 "acceptSslCerts": false, 49 "applicationCacheEnabled": false, 50 "browserConnectionEnabled": false, 51 "browserName": "chrome", 52 "chrome.chromedriverVersion": "26.0.1383.0", 53 "cssSelectorsEnabled": true, 54 "databaseEnabled": false, 55 "handlesAlerts": true, 56 "javascriptEnabled": true, 57 "locationContextEnabled": false, 58 "nativeEvents": true, 59 "platform": "linux", 60 "rotatable": false, 61 "takesScreenshot": true, 62 "version": "28.0.1500.95", 63 "webStorageEnabled": true 64 } 65} The 'WaitForAllTabsToStopLoading' issue seems to be a long-resolved issue with chromedriver (see http://code.google.com/p/selenium/issues/detail?id=2996), so why is this still happening when these test run via CloudBees/SauceLabs?