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

Try removing isolate.kill() #2198

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Try removing isolate.kill() #2198

wants to merge 1 commit into from

Conversation

natebosch
Copy link
Member

@natebosch natebosch commented Mar 22, 2024

Originally isolates were killed when the loader was closed as the runner
is shutting down. There was no comment in the review about the specific
reason for isolate.kill(). https://codereview.chromium.org//920703006

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

No internal tests seem to be relying on this behavior, and nothing times
out when it is removed. I am unable to find a counter-example or a way
to write a test for this behavior, so remove it for now.

@natebosch natebosch force-pushed the remove-isolate-kill branch from 4e0db3f to d65ea4d Compare March 22, 2024 18:10
Originally isolates were killed when the loader was closed as the runner
is shutting down. There was no comment in the review about the specific
reason for `isolate.kill()`. https://codereview.chromium.org//920703006

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

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.
@natebosch natebosch force-pushed the remove-isolate-kill branch from d65ea4d to ef7c98d Compare March 22, 2024 18:13
@natebosch
Copy link
Member Author

After some internal discussion and thinking more about the intent in https://codereview.chromium.org//1206033004 this isolate.kill is not here for correctness, but to reduce concurrent resource use when running multiple VM tests suites in sequence. It probably isn't tested because that's a hard test to write.

We should consider writing an integration test that uses the VM service to count how many isolates are active or something along those lines.

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

Successfully merging this pull request may close these issues.

1 participant