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

Allow configuring SIGKILL timeout #2457

Closed
karan-kang opened this issue Nov 15, 2016 · 2 comments
Closed

Allow configuring SIGKILL timeout #2457

karan-kang opened this issue Nov 15, 2016 · 2 comments

Comments

@karan-kang
Copy link

karan-kang commented Nov 15, 2016

The SIGKILL timeout is currently hardocoded in launcher\process.js file. On our CI build server, the process exit takes longer than 2 seconds when running large number of tests, as the process exit waits for all Chrome child processes to be killed.

Is it possible to make this timeout configurable?

"gulp": "~3.9.1",
"karma": "~1.3.0",
"karma-chrome-launcher": "~2.0.0",
"karma-coverage": "~1.1.1",
"karma-html-reporter": "~0.2.7",
"karma-junit-reporter": "~1.1.0",
"karma-nested-reporter": "~0.1.4",
"karma-jasmine": "~1.0.2",
"karma-jasmine-runner2-reporter": "~0.3.5"

@vivganes
Copy link
Contributor

@Karankang007 This issue seems to be a duplicate of already reported issue: #2447

Can you please take a look at it and close this issue if this is a duplicate?

There is a possibility that I am wrong in my understanding.

@maksimr
Copy link
Contributor

maksimr commented Nov 25, 2016

Close as duplicate #2447

@maksimr maksimr closed this as completed Nov 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants