58a51c2ce9
run.bash holds a persistent refcount file in the shared state directory so multiple concurrent tests can share a single container. If a prior test_all run is killed (e.g. Ctrl-C), the count never reaches zero on the next run and the container is never stopped - forcing manual cleanup. Three fixes, all in fstest/testserver/init.d/run.bash: - On start, if the refcount is non-zero but no container is running, treat it as zero. Stops leaking through future runs. - reset now rm -rfs RUN_ROOT (the per-server state) instead of RUN_BASE (the shared parent) which was clobbering sibling services. - New force-stop verb unconditionally stops the container and zeroes the refcount. This is the primitive that the Go-side cleanup sweep will call at end-of-run.
This directory contains scripts to start and stop servers for testing.
The commands are named after the remotes in use. They are executable files with the following parameters:
start - starts the server if not running
stop - stops the server if nothing is using it
status - returns non-zero exit code if the server is not running
reset - stops the server and resets any reference counts
These will be called automatically by test_all if that remote is required.
When start is run it should output config parameters for that remote.
If a _connect parameter is output then that will be used for a
connection test. For example if _connect=127.0.0.1:80 then a TCP
connection will be made to 127.0.0.1:80 and only when that succeeds
will the test continue.
If in addition to _connect, _connect_delay=5s is also present then
after the connection succeeds rclone will wait 5s before continuing.
This is for servers that aren't quite ready even though they have
opened their TCP ports.
Writing new scripts
A docker based server or an rclone serve based server should be easy
to write. Look at one of the examples.
run.bash contains boilerplate to be included in a bash script for
interpreting the command line parameters. This does reference counting
to ensure multiple copies of the server aren't running at once.
Including this is mandatory. It will call your start(), stop() and
status() functions.
docker.bash contains library functions to help with docker
implementations. It contains implementations of stop() and
status() so all you have to do is write a start() function.
rclone-serve.bash contains functions to help with rclone serve
based implementations. It contains implementations of stop() and
status() so all you have to do is write a start() function which
should call the run() function provided.
Any external TCP or UDP ports used should be unique as any of the servers might be running together. So please create a new line in the PORTS file to allocate your server a port. Bind any ports to localhost so they aren't accessible externally.