-
-
Save tfnico/8471223 to your computer and use it in GitHub Desktop.
> node_modules/protractor/bin/protractor src/test/js/e2e/protractor_phantom.js | |
Starting selenium standalone server... | |
Selenium standalone server started at http://192.168.178.59:51258/wd/hub | |
F | |
Failures: | |
1) homepage should show notification after starting import | |
Message: | |
UnknownError: Error communicating with the remote browser. It may have died. | |
Build info: version: '2.39.0', revision: 'ff23eac', time: '2013-12-16 16:11:15' | |
System info: host: 'Thomas-Ferris-Nicolaisens-iMac.local', ip: '192.168.178.59', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.8.5', java.version: '1.7.0_45' | |
Driver info: driver.version: EventFiringWebDriver | |
Stacktrace: | |
UnknownError: Error communicating with the remote browser. It may have died. | |
Build info: version: '2.39.0', revision: 'ff23eac', time: '2013-12-16 16:11:15' | |
System info: host: 'Thomas-Ferris-Nicolaisens-iMac.local', ip: '192.168.178.59', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.8.5', java.version: '1.7.0_45' | |
Driver info: driver.version: EventFiringWebDriver | |
==== async task ==== | |
WebDriver.navigate().to(about:blank) | |
at Protractor.get (/Users/tfnico/projects/vplan/dispatcher/node_modules/protractor/lib/protractor.js:519:15) | |
at null.<anonymous> (/Users/tfnico/projects/vplan/dispatcher/src/test/js/e2e/excel_import_spec.js:28:17) | |
at /Users/tfnico/projects/vplan/dispatcher/node_modules/protractor/jasminewd/index.js:54:12 | |
at wrapper [as _onTimeout] (timers.js:252:14) | |
==== async task ==== | |
at null.<anonymous> (/Users/tfnico/projects/vplan/dispatcher/node_modules/protractor/jasminewd/index.js:53:12) | |
at null.<anonymous> (/Users/tfnico/projects/vplan/dispatcher/node_modules/protractor/node_modules/minijasminenode/lib/async-callback.js:45:37) | |
at Timer.listOnTimeout [as ontimeout] (timers.js:110:15) |
Any development with this issue?
I have the same issue on
-Windows 7 64
- Protractor 1.6.1 (run either through grunt-protractor-runner 1.2.1 or directly in shell)
- Selenium 2.43.1
- PhantomJS 1.9.8
Protractor outputs:
UnknownError: Error communicating with the remote browser. It may have died.
Build info: version: '2.43.1', revision: '5163bce', time: '2014-09-10 16:27:33'
System info: host: 'MCAW7016', ip: '192.168.35.173', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.7.0_51'
Driver info: driver.version: EventFiringWebDriver
at new bot.Error (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\atoms\error.js:109:18)
at Object.bot.response.checkResponse (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\atoms\response.js:106:9)
at c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:277:20
at c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\goog\base.js:1243:15
at webdriver.promise.ControlFlow.runInNewFrame_ (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:1539:20)
at notify (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:362:12)
at notifyAll (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:331:7)
at resolve (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:309:7)
at fulfill (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:429:5)
at c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:1406:10
==== async task ====
WebDriver.quit()
at webdriver.WebDriver.schedule (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:268:15)
at webdriver.WebDriver.quit (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:333:21)
at HostedDriverProvider.teardownEnv (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\lib\driverProviders\hosted.js:38:16)
at driverprovider_.setupEnv.then.then.then.then.passed (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\lib\runner.js:264:35)
at _fulfilled (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:797:54)
at self.promiseDispatch.done (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:826:30)
at Promise.promise.promiseDispatch (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:759:13)
at c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:573:44
at flush (c:\Users\jberube\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:108:17)
+1 me too. same issue.
Any development with this issue? I have the same issue
Try this one - in the beforeEach:
browser.ignoreSynchronization = true; browser.get('/'); browser.waitForAngular();
+1 to @barzik approach, I had PhantomJS crashing hard after a test not finding an element by id and giving false negatives all across the board because the browser was down. This lines gave us a workaround the browser crashing and helprf us to get the tests reporing the error properly.
+1 to @barzik, thank you :)
same here
@barzik solution works fine, thank you
+1 to @barzik thank you
In fact, @barzik solution solved my problem with the PhantomJS server but now I've resolution issues on my screenshots tests.
[EDIT] I'm sorry I didn't realize I was posting on a project specific thread, but this seems to be more general so I'll leave this here anyway, feel free to delete this comment.
I'm having the same issue, some times tests run fine, some times it crashes after a random amount of them, the only clue I have so far is that it almost never fails on my local dev env, but it fails about 50% of the time on the CI server.
Here's the console output (those same tests run fine in oher builds)
And I don't see anything suspicious in the phantom driver log either: