Previously, we asserted that SIGKILLing a process right after SIGTERMing it would have not effect because the process should have already processed the SIGTERM and closed if it were going to terminate graciously. Working with 'xcrun simctl spawn' and API tests which timeout, however, this observation is not correct. When 'xcrun simctl spawn' receives a SIGKILL right after a SIGTERM, it will not propagate the SIGTERM to it's child process, leaving an orphaned process.
Created attachment 339199 [details] Patch
This hasn't bit us yet, but the moment someone commits an iOS test which times out, it will.
Comment on attachment 339199 [details] Patch r=me
Comment on attachment 339199 [details] Patch Going to wait for EWS since I only tested iOS API tests, and this code path is used by everything for layout tests.
Comment on attachment 339199 [details] Patch Attachment 339199 [details] did not pass win-ews (win): Output: http://webkit-queues.webkit.org/results/7525427 New failing tests: http/tests/security/canvas-remote-read-remote-video-localhost.html
Created attachment 339203 [details] Archive of layout-test-results from ews200 for win-future The attached test failures were seen while running run-webkit-tests on the win-ews. Bot: ews200 Port: win-future Platform: CYGWIN_NT-6.1-2.9.0-0.318-5-3-x86_64-64bit
Created attachment 339207 [details] Patch
Comment on attachment 339207 [details] Patch Clearing flags on attachment: 339207 Committed r231209: <https://trac.webkit.org/changeset/231209>
All reviewed patches have been landed. Closing bug.
<rdar://problem/39877451>