protractor: Launcher uncaught exception
Should log the error if the error is unknown and is being thrown.
lib/launcher.ts#L182
} else {
logger.error(e);
process.exit(ProtractorError.CODE);
}
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 1
- Comments: 22 (9 by maintainers)
Commits related to this issue
- fix(launcher): output uncaught exception error closes #3384 — committed to cnishina/protractor by cnishina 8 years ago
- fix(launcher): output uncaught exception error (#3390) * split out message and stack to hopefully provide more information to the error closes #3384 — committed to angular/protractor by cnishina 8 years ago
- revert protractor to 3.3.0 for now until this fix is released https://github.com/angular/protractor/issues/3384 — committed to tjgrathwell/ng-picross by tjgrathwell 8 years ago
@cnishina i think that version 4.0.0 suffer of various instabilities.
i was having the issue of this ticket; now that i disclosed the error with your suggestion i get:
./node_modules/protractor/bin/protractor tests/end2end/protractor-coverage.config.js [17:51:07] I/local - Starting selenium standalone server… [17:51:07] I/launcher - Running 1 instances of WebDriver [17:51:08] I/local - Selenium standalone server started at http://10.13.17.141:39838/wd/hub [17:51:10] E/launcher - { [WebDriverError: Connection reset] name: ‘WebDriverError’ } [17:51:10] E/launcher - Process exited with error code 199
it seems that passing from protractor binary, the ip choosen for the selenium webdriver is a randomom one from the pool of the laptop of the user and this causes errors depending on the network configuration.
i would suggest that you allow the user to specify the address of the standalone selenium or you adopt forcefully the 127.0.0.1
Having similar issue here - allways seeing this at end of (successfully executed) tests:
with protractor 4.0.0. and chromedriver 2.22 - did not have this before the update to 4.0.0 - our tests did run without these problems before. and the chrome browser does not get closed anymore now (seems to fail there somehow).