Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues exiting chromedriver on windows #22094

Closed
liza-mae opened this issue Aug 16, 2018 · 2 comments
Closed

Issues exiting chromedriver on windows #22094

liza-mae opened this issue Aug 16, 2018 · 2 comments
Assignees
Labels
Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc test_infra test

Comments

@liza-mae
Copy link
Contributor

liza-mae commented Aug 16, 2018

I am getting this error exiting chromedriver on Windows. I am only seeing this intermittently but mainly with using chrome headless.

C:/Users/vagrant/Final/kibana/test/functional/services/remote/browser_driver_api/browser_driver_local_api.js:66
api.emit('error', new Error(driverName + exited with code ${code}));
^
Error: chromedriver exited with code 1
at ChildProcess.proc.on.code (C:/Users/vagrant/Final/kibana/test/functional/services/remote/browser_driver_api/browser_driver_local_api.js
:66:29)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)

So tried to hide the error. Changed line 65 in test/functional/services/remote/browser_driver_api/browser_driver_local_api.js to be an &&

But now I get this error:
ERROR Error: Command failed: taskkill /pid 2976 /T /F
ERROR: The process with PID 5536 (child process of PID 4712) could not be terminated.
Reason: The operation attempted is not supported.
ERROR: The process with PID 5780 (child process of PID 4712) could not be terminated.
Reason: The operation attempted is not supported.
ERROR: The process with PID 4712 (child process of PID 2976) could not be terminated.
Reason: There is no running instance of the task.

      at ChildProcess.exithandler (child_process.js:275:12)
      at emitTwo (events.js:126:13)
      at ChildProcess.emit (events.js:214:7)
      at maybeClose (internal/child_process.js:925:16)
      at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

I don't see chrome in task manager after the tests ends.

Spencer want to look at possibly replacing tree-kill and also referenced the issue below:

https://www.npmjs.com/package/tree-kill

puppeteer/puppeteer#1047

cc: @spalger

Part of issue: #21315

@liza-mae
Copy link
Contributor Author

cc: @tylersmalley

@jbudz jbudz added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Oct 10, 2018
@liza-mae
Copy link
Contributor Author

Closing per #22224

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc test_infra test
Projects
None yet
Development

No branches or pull requests

2 participants