Commit d65ea4d
committed
Try removing isolate.kill()
At one point isolates were killed when the loader was closed as the
runner is shutting down. Later the kill was moved to when the test suite
is done. There was no specific comment about the `isolate.kill()`
changes. https://codereview.chromium.org//1206033004
Before that the `isolate.kill` on close goes back to the original
implementation of the loader.
https://codereview.chromium.org//920703006
No internal tests seem to be relying on this behavior, and nothing times
out when it is removed.
Check whether there are any tests on CI that validate this behavior.1 parent 6a4e75a commit d65ea4d
1 file changed
+0
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
80 | 80 | | |
81 | 81 | | |
82 | 82 | | |
83 | | - | |
84 | 83 | | |
85 | 84 | | |
86 | 85 | | |
| |||
0 commit comments