Attention is currently required from: daniel, fixeria, pespin.

Hello Jenkins Builder, daniel, fixeria, pespin,

I'd like you to reexamine a change. Please visit

https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37694?usp=email

to look at the new patch set (#2).

The following approvals got outdated and were removed: Verified+1 by Jenkins Builder

Change subject: testenv: add test environment script ......................................................................

testenv: add test environment script

Add a new testenv.py script that builds/installs all components needed for a testsuite, builds the testsuite from source and runs it.

Features: * --binary-repo argument to install packages from osmocom:latest or any other repository from the Osmocom OBS instead of building from source * without --binary-repo, the test components are built with osmo-dev, cloning the missing source git repositories and building them in the right order * --podman argument to run the testsuite and its components inside a container (using podman instead of docker so it runs rootless) * Simple testenv.cfg file to specify components for running testsuites * Iterative compilation of components and testsuite * Using ccache * Testsuite doesn't start if any of the components fail to start (e.g. because of a config error) * Testsuite gets stopped if any of the components crash * ^C stops the testsuite + all components * Test component output logs to stdout in addition to a log file (turn off with --no-tee) * --test argument to only run one specific test * --shell argument to run an interactive shell before teardown to inspect the test environment while components are still running

This script unifies the use cases of running a testsuite without containers (for local development), and with containers (as jenkins runs it, but can also be used for local development e.g. to get a clean pcap). Previously jenkins used a different set of configurations from docker-playground.git and many different containers instead of just one.

This patch contains the seccomp_profile.json for enabling io_uring, from docker-playground I27567c2a5d9543c3509c316226c082ab950c5ebc.

Related: OS#6494 Change-Id: If9f8b79dd6e5b4f06be4e5ff73db97759c3acfb2 --- M .gitignore M README.md A _testenv/README.md A _testenv/data/osmo-dev/osmo-bts-trx.opts A _testenv/data/podman/Dockerfile A _testenv/data/podman/obs.key A _testenv/data/podman/seccomp_profile.json A _testenv/data/scripts/log_format.sh A _testenv/data/scripts/rename_junit_xml_classname.sh A _testenv/data/scripts/respawn.sh A _testenv/data/scripts/testenv-podman-main.sh A _testenv/testenv.py A _testenv/testenv/__init__.py A _testenv/testenv/cmd.py A _testenv/testenv/daemons.py A _testenv/testenv/osmo_dev.py A _testenv/testenv/podman.py A _testenv/testenv/podman_install.py A _testenv/testenv/requirements.py A _testenv/testenv/testdir.py A _testenv/testenv/testenv_cfg.py A _testenv/testenv/testsuite.py A testenv.py 23 files changed, 3,000 insertions(+), 0 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/94/37694/2