Skip to content

Attach obfuscated backtraces to public logs in case of unexpected error #955

Attach obfuscated backtraces to public logs in case of unexpected error

Attach obfuscated backtraces to public logs in case of unexpected error #955

Workflow file for this run

name: Build Test
on:
push:
branches: [ master ]
pull_request:
branches: [ master ]
jobs:
linters-deb-testing:
name: Static Checks (Debian Testing)
runs-on: ubuntu-24.04
steps:
- uses: actions/checkout@v3
- name: Create Native Environment
run: cd tests/ci/ && podman build -t laniakea -f ./Dockerfile-debian-testing .
- name: Set up Python virtual environment
run: podman run -a stdout -a stderr -v `pwd`:/build laniakea
./tests/ci/run-venv-prepare.sh lint-only
- name: Check
# FIXME: Ignore any failures for now until we have ported to SQLAlchemy >= 2.0
continue-on-error: true
run: podman run -a stdout -a stderr -v `pwd`:/build laniakea
./tests/ci/run-lint.sh
test-deb-bullseye:
name: Testsuite (Debian 12)
runs-on: ubuntu-24.04
steps:
- uses: actions/checkout@v3
- name: Create Native Environment
run: cd tests/ci/ && podman build -t laniakea -f ./Dockerfile-debian-stable .
- name: Set up Python virtual environment
run: podman run -a stdout -a stderr -v `pwd`:/build laniakea
./tests/ci/run-venv-prepare.sh
- name: Testsuite
run: podman run --privileged -a stdout -a stderr --security-opt seccomp=unconfined -v `pwd`:/build laniakea
./tests/ci/run-tests.sh