Skip to content

Fixed #79: using binary notation and better limit faq wording #190

Fixed #79: using binary notation and better limit faq wording

Fixed #79: using binary notation and better limit faq wording #190

Workflow file for this run

name: Tests
on:
pull_request:
paths:
- "backend/**"
push:
branches: [ main ]
env:
POSTGRES_URI: "postgresql+psycopg://nautilus:nautilus@localhost:5432/nautilus"
S3_URL_WITH_CREDENTIALS: "PLACEHOLDER"
PRIVATE_SALT: "PRIVATE_SALT"
jobs:
run-tests:
runs-on: ubuntu-22.04
services:
postgres:
image: postgres:15.3-bullseye
env:
POSTGRES_PASSWORD: nautilus
POSTGRES_DB: nautilus
POSTGRES_PORT: 5432
POSTGRES_USER: nautilus
ports:
# Maps tcp port 5432 on service container to the host
- 5432:5432
steps:
- uses: actions/checkout@v3
- name: Set up Python
uses: actions/setup-python@v4
with:
python-version-file: "backend/pyproject.toml"
architecture: x64
- name: Install dependencies (and project)
working-directory: backend
run: |
pip install -U pip
pip install -e .[test,scripts]
- name: Initialize the database
working-directory: backend
run: |
alembic upgrade head
alembic check
- name: Run the tests
working-directory: backend
run: inv coverage --args "-vvv"
- name: Upload coverage to Codecov
uses: codecov/codecov-action@v4
with:
directory: backend
fail_ci_if_error: true
token: ${{ secrets.CODECOV_TOKEN }}
- name: Ensure we can build targets
working-directory: backend
run: |
pip install build
python3 -m build