Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

Local DriverProvider does not shutdown Chromedriver #3779

Closed
cnishina opened this issue Dec 1, 2016 · 1 comment · Fixed by #3787
Closed

Local DriverProvider does not shutdown Chromedriver #3779

cnishina opened this issue Dec 1, 2016 · 1 comment · Fixed by #3787
Assignees
@cnishina
Labels
type: bug

Comments

@cnishina
Copy link
Member

cnishina commented Dec 1, 2016

Some of the logs are located here: #3772

When driver provider is local, on shutdown the server stops; however, chromedrivers are left in the background running. This is what's left after running the test 4 times.

cnishina         69541   0.0  0.1  2576860   9732 s001  S    11:16AM   0:00.04 /Users/cnishina/src/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.25 --port=21178
cnishina         60723   0.0  0.1  2576860   9336   ??  S     6:02PM   0:00.03 /Users/cnishina/src/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.25 --port=44325
cnishina         60318   0.0  0.1  2576860   9340   ??  S     5:58PM   0:00.03 /Users/cnishina/src/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.25 --port=42154
cnishina         70323   0.0  0.1  2577908   9644 s001  S    11:19AM   0:00.04 /Users/cnishina/src/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.25 --port=33676
@cnishina cnishina self-assigned this Dec 1, 2016
@cnishina
Copy link
Member Author

cnishina commented Dec 1, 2016 •
edited
Loading

Note to self...fix nit: browser line 324. comment should be sentences.

cnishina added a commit to cnishina/protractor that referenced this issue Dec 2, 2016
@cnishina
fix(driverProviders): quit forked instances w/ local driver provider
cf701e1 
- 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
cnishina added a commit to cnishina/protractor that referenced this issue Dec 2, 2016
@cnishina
fix(driverProviders): quit forked instances w/ local driver provider
9442cbd 
- 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
@cnishina cnishina mentioned this issue Dec 2, 2016
Merged
sjelin pushed a commit that referenced this issue Dec 3, 2016
@cnishina @sjelin
fix(driverProviders): quit forked instances w/ local driver provider (#…
742f264 
…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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@cnishina cnishina

Labels
type: bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(driverProviders): quit forked instances w/ local driver provider cnishina/protractor
1 participant
@cnishina