Spawn a new process for the test runner #11064
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dfandrich
force-pushed
the
dfandrich/pr11064
branch
2 times, most recently
from
469baa8 to
f5ece5b
Compare
dfandrich
added a commit
that referenced
this pull request
May 3, 2023
When the -j option is given, a new process is spawned in which the test programs are run and from which test servers are started. Only one process can be started at once, but this is sufficient to test that the infrastructure can isolate those functions in a new task. There should be no visible difference between the two modes at the moment. Ref: #10818 Closes #11064
dfandrich
force-pushed
the
dfandrich/pr11064
branch
from
f5ece5b to
c1f2829
Compare
This will no longer be static soon. Ref: #10818
Some recent refactoring made these export no longer necessary. Also, stop displaying the Unix socket paths at startup since there will soon be many of them and they're not that interesting. Ref: #10818
There will soon be multiple log directories so the paths will no longer be static in runtests.pl. Also, get rid of $SERVER2IN which was not used. Ref: #10818
This sets up the runner environment to start running tests. Ref: #10818
This is where citest_starttest is called. Ref: #10818
Program arguments are marshalled and then written to the end of a pipe which is later read from and the arguments unmarshalled before the desired function is called normally. The function return values are then marshalled and written into another pipe when is later read from and unmarshalled before being returned to the caller. The implementation is currently blocking but can be made non-blocking without any changes to the API. This allows calling multiple runners without blocking in the future. Ref: #10818
This allows it to run in a non-blocking manner. Ref: #10818
When the -j option is given, a new process is spawned in which the test programs are run and from which test servers are started. Only one process can be started at once, but this is sufficient to test that the infrastructure can isolate those functions in a new task. There should be no visible difference between the two modes at the moment. Ref: #10818 Closes #11064
The controller currently only creates and uses one, but more are now possible. Ref: #10818
dfandrich
force-pushed
the
dfandrich/pr11064
branch
from
c1f2829 to
8009fb2
Compare
bch
pushed a commit
to bch/curl
that referenced
this pull request
Jul 19, 2023
When the -j option is given, a new process is spawned in which the test programs are run and from which test servers are started. Only one process can be started at once, but this is sufficient to test that the infrastructure can isolate those functions in a new task. There should be no visible difference between the two modes at the moment. Ref: curl#10818 Closes curl#11064
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is optional (default disabled) and is controlled by the -j flag. It
currently supports at most 1 runner which will fork() a new process that takes
care of running curl for the actual test. This proves the groundwork to handle
tests in multiple processes has been laid.