Issues exiting chromedriver on windows #22094
Labels
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
test_infra
test
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.
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
The text was updated successfully, but these errors were encountered: