Local DriverProvider Forked Browser issue returns error code 135 #3772
Comments
|
Please follow the template instructions for creating an issue. Please provide a protractor config and an example of what created the stacktrace. |
|
@cnishina launching any test causes that issue. My protractor config is Note that I don't set the variable SELENIUM_ADDRESS. It looks like to starts a driver by itself, but at the end it is not able to shut it down. |
|
You still need Also, after stopping those instances, I would recommend just using Since this appears to be more of a setup question, I'm going to close this. Please ask your support questions on StackOverflow, Google Group discussion list, or Gitter. For more information please reference https://github.com/angular/protractor/blob/master/CONTRIBUTING.md#questions Thank you! |
|
@cnishina, I think It is protractor that launches all those selenium drivers. It looks like It has a mechanism to instantiate the driver but not to shut it down. I consider it a bug, my expectation were that an error was thrown if web-driver was not manually launched by me. Or, if you are adding automatic creation of the webdriver, I expect that protractor shuts it down correctly. If you see the error, it is quite explicit. It comes from protractor. |
|
According to your config, Protractor is using the selenium address which means you have already started the selenium standalone server. I would suggest trying out my suggestions above. |
|
My selenium address is undefined. So protractor generates it dynamically every time (on a different port) I start protractor. |
|
One more question: are you forking the browser? |
|
Yes, but on in the all tests. This happens at the startup of protractor, when there are not yet 2 browsers. |
|
So I am able to reproduce this via |
|
@bitliner I would recommend using |
|
So there's several things going on with this:
For part 1: This is my current stack trace on PR #3766 when using local. |
cnishina
changed the title
Error code: 135
cnishina
changed the title
- fix driver provider quit session to not throw error and quit - should fix sauce labs test, enabling expected conditions test with forked instance - checked that chromedriver does not persist in the background - add local driver test with forked instance to test suite - organize attach session and local specs to driverProviders directory closes angular#3780, closes angular#3779, closes angular#3772
- fix driver provider quit session to not throw error and quit - should fix sauce labs test, enabling expected conditions test with forked instance - checked that chromedriver does not persist in the background - add local driver test with forked instance to test suite - organize attach session and local specs to driverProviders directory closes angular#3780, closes angular#3779, closes angular#3772
…3787) - fix driver provider quit session to not throw error and quit - should fix sauce labs test, enabling expected conditions test with forked instance - checked that chromedriver does not persist in the background - add local driver test with forked instance to test suite - organize attach session and local specs to driverProviders directory closes #3780, closes #3779, closes #3772
v6.9.1Version 4.0.111.5.6ChromeMac OSIt throws the following error when tests are finished.
The selenium driver start at:
A funny part is that I don't set any selenium address int eh configuration file, and it is going to use drivers that are in background that looks like coming from previous run, and I was not aware they were running in the background.
I never launched all these webdrivers in the background.
It looks like
webdriver startis run automatically by protractor, and there is no need anymore for it. But then, those processes are never killed.The text was updated successfully, but these errors were encountered: