fix(docker): use logging.prod.conf for sharness

Signed-off-by: Kevin Morris <kevr@0cost.org>
This commit is contained in:
Kevin Morris 2021-12-07 13:44:13 -08:00
parent 409229739e
commit 7831503c19
No known key found for this signature in database
GPG key ID: F7E46DED420788F3
3 changed files with 10 additions and 1 deletions

View file

@ -275,7 +275,7 @@ services:
init: true
environment:
- AUR_CONFIG=conf/config.sqlite
entrypoint: /docker/test-sqlite-entrypoint.sh
entrypoint: /docker/sharness-entrypoint.sh
command: /docker/scripts/run-sharness.sh
stdin_open: true
tty: true

View file

@ -6,7 +6,10 @@ dir=$(dirname $0)
make -C test clean
# Run sharness tests.
cp -vf logging.conf logging.conf.bak
cp -vf logging.prod.conf logging.conf
bash $dir/run-sharness.sh
cp -vf logging.conf.bak logging.conf
# Run Python tests with MariaDB database.
# Pass --silence to avoid reporting coverage. We will do that below.

6
docker/sharness-entrypoint.sh Executable file
View file

@ -0,0 +1,6 @@
#!/bin/bash
set -eou pipefail
cp -vf logging.prod.conf logging.conf
exec "$@"