You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 31, 2020. It is now read-only.
Each test case launches a python process to run it. There was a significant performance improvement from the changes made to the JS test runner by having a persistent process. It may be possible to use the same structure as was used in #789 to launch a single child process and send it code to execute, only terminating it and starting a new one in the case of a test timing out.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Similar to the updates made by #783 and #789.
Each test case launches a python process to run it. There was a significant performance improvement from the changes made to the JS test runner by having a persistent process. It may be possible to use the same structure as was used in #789 to launch a single child process and send it code to execute, only terminating it and starting a new one in the case of a test timing out.
The text was updated successfully, but these errors were encountered: