Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upIssue 4030: Using SIGKILL instead of SIGTERM to terminate the process on timeout #4036
Conversation
|
We could try SIGTERM first and then SIGKILL (1m after), what do you all think? |
that sgtm. or add an env variable for the build machines which need SIGKILL |
I'll add an environment variable. @mihaiplesa: let me know if EDIT: Updated @mihaiplesa @diracdeltas - let me know if the code looks good now |
|
We have a var named |
… on timeout.
|
have tested and works as expected |
change she requested as made with 7ef06af
Issue 4030: Using SIGKILL instead of SIGTERM to terminate the process on timeout
Issue 4030: Using SIGKILL instead of SIGTERM to terminate the process on timeout
jumde commentedApr 5, 2019
•
edited
fix #4030
PR Builder passed here: https://staging.ci.brave.com/job/brave-browser-build-pr/job/PR-4036/4/
Submitter Checklist:
npm test brave_unit_tests && npm test brave_browser_tests && npm run test-security) ongit rebase master(if needed).git rebase -ito squash commits (if needed).Test Plan:
npm run test-securityworks on build machines.lib/whitelistedUrlPrefixes.jsand confirm it fails.Reviewer Checklist: