Skip to content

Latest commit

 

History

History
110 lines (80 loc) · 4.04 KB

README.md

File metadata and controls

110 lines (80 loc) · 4.04 KB
Raw

SyTest Docker Images

These Dockerfiles create containers for running SyTest in various configurations. SyTest is not included in these images (see Selecting a checkout of SyTest), but its dependencies are.

Included currently is:

  • matrixdotorg/sytest Base container with SyTest dependencies installed
    • Tagged by underlying Debian/Ubuntu image: bullseye or testing
  • matrixdotorg/sytest-synapse: Runs SyTest against Synapse
    • Tagged by underlying Debian/Ubuntu image: bullseye or testing

Target-specific details

Synapse

The sytest-synapse images expect a checkout of the synapse git repository to be mounted at /src; additionally, server logs will be written to /logs, so it is useful to mount a volume there too.

For example:

docker run --rm -it -v /path/to/synapse\:/src:ro -v /path/to/where/you/want/logs\:/logs matrixdotorg/sytest-synapse:bullseye

The following environment variables can be set with -e to control the test run:

  • POSTGRES: set non-empty to test against a PostgreSQL database instead of SQLite.
  • MULTI_POSTGRES: set non-empty (along with POSTGRES) to test against multiple PostgreSQL databases where the main store and state store are split.
  • WORKERS: set non-empty to test a worker-mode deployment rather than a monolith. Requires POSTGRES.
  • ASYNCIO_REACTOR: set non-empty to test with the Twisted asyncio reactor enabled
  • OFFLINE: set non-empty to avoid updating the python or perl dependencies.
  • BLACKLIST: set non-empty to change the default blacklist file to the specified path relative to the Synapse directory
  • TIMEOUT_FACTOR: sets a number that test timeouts are multiplied by.

An example of running Synapse in worker mode:

docker run --rm -it -e POSTGRES=1 -e WORKERS=1 -v /path/to/synapse\:/src:ro \
    -v /path/to/where/you/want/logs\:/logs matrixdotorg/sytest-synapse:bullseye

Dendrite

The sytest-dendrite images expect a checkout of the dendrite git repository to be mounted at /src; additionally, server logs will be written to /logs, so it is useful to mount a volume there too.

docker run --rm -it -v /path/to/dendrite\:/src:ro -v /path/to/where/you/want/logs\:/logs matrixdotorg/sytest-dendrite

Selecting a checkout of Sytest

The images do not contain a copy of Sytest; by default, they download an appropriate branch of Sytest. Normally this is either a branch with the same name as that of the target homeserver, or develop. This can be overridden with the environment variable SYTEST_BRANCH, for example:

docker run --rm -it \
    -e SYTEST_BRANCH="my-sytest-branch"
    -v /path/to/synapse\:/src:ro -v /path/to/where/you/want/logs\:/logs
    matrixdotorg/sytest-synapse:bullseye

If the branch referred to by SYTEST_BRANCH does not exist, develop is used instead.

If you would like to run tests with an existing checkout of Sytest, add a volume to the docker command mounting the checkout to the /sytest folder in the container:

docker run --rm -it -v /path/to/synapse\:/src:ro -v /path/to/where/you/want/logs\:/logs \
    -v /path/to/code/sytest\:/sytest:ro matrixdotorg/sytest-synapse:bullseye

Running a single test file, and other sytest commandline options

You can pass arguments to sytest by adding them at the end of the docker command. For example:

docker run --rm -it ... matrixdotorg/sytest-synapse:bullseye tests/20profile-events.pl

Building the containers

These are automatically built and deployed on the develop branch by GitHub Actions. See .github/workflows.docker.yml for the gory details.

Loading sytest plugins at start

To utilize sytest plugins and automatically load them on start set the PLUGINS environment variable. This should be one or more URLs to tar.gz files separated by whitespaces.

The bootstrap script will search for ${SYTEST_TARGET}_sytest.sh in all plugins. This can be used to execute custom scripts like the ones in /scripts/

docker run --rm -it -e PLUGINS="https://host/path/to/hs_plugin.tar.gz https://host2/path/to/output_plugin.tar.gz"