Files
aitbc/.gitea/workflows/python-tests.yml
aitbc a2f84648ab
Some checks failed
API Endpoint Tests / test-api-endpoints (push) Successful in 9s
CLI Tests / test-cli (push) Failing after 6m49s
Integration Tests / test-service-integration (push) Successful in 2m22s
Package Tests / Python package - aitbc-agent-sdk (push) Failing after 26s
Package Tests / Python package - aitbc-core (push) Failing after 10s
Package Tests / Python package - aitbc-crypto (push) Failing after 5s
Package Tests / Python package - aitbc-sdk (push) Failing after 2s
Package Tests / JavaScript package - aitbc-sdk-js (push) Successful in 7s
Package Tests / JavaScript package - aitbc-token (push) Successful in 16s
Production Tests / Production Integration Tests (push) Failing after 1m21s
Python Tests / test-python (push) Has been cancelled
Security Scanning / security-scan (push) Failing after 13s
Staking Tests / test-staking-service (push) Failing after 1m13s
Staking Tests / test-staking-integration (push) Has been skipped
Staking Tests / test-staking-contract (push) Has been skipped
Staking Tests / run-staking-test-runner (push) Has been skipped
ci: standardize Python venv setup across all workflows using setup-python-venv.sh script
Replaced manual venv creation and pip install commands with calls to scripts/ci/setup-python-venv.sh across all CI workflows. The script provides consistent venv setup with configurable options for requirements installation, copy mode, and extra packages.

- Changed from manual `python3 -m venv` + `pip install` to setup-python-venv.sh in all workflows
- Added --skip-requirements flag where workflows don't need requirements
2026-04-19 21:05:26 +02:00

87 lines
2.6 KiB
YAML

name: Python Tests
on:
push:
branches: [main, develop]
paths:
- 'apps/**/*.py'
- 'packages/py/**'
- 'tests/**'
- 'pyproject.toml'
- 'requirements.txt'
- '.gitea/workflows/python-tests.yml'
pull_request:
branches: [main, develop]
workflow_dispatch:
concurrency:
group: python-tests-${{ github.ref }}
cancel-in-progress: true
jobs:
test-python:
runs-on: debian
timeout-minutes: 15
steps:
- name: Clone repository
run: |
WORKSPACE="/var/lib/aitbc-workspaces/python-tests"
rm -rf "$WORKSPACE"
mkdir -p "$WORKSPACE"
cd "$WORKSPACE"
git clone --depth 1 http://gitea.bubuit.net:3000/oib/aitbc.git repo
- name: Setup Python environment
run: |
cd /var/lib/aitbc-workspaces/python-tests/repo
# Ensure standard directories exist
mkdir -p /var/lib/aitbc/data /var/lib/aitbc/keystore /etc/aitbc /var/log/aitbc
bash scripts/ci/setup-python-venv.sh \
--repo-dir "$PWD" \
--venv-dir "$PWD/venv" \
--mode copy \
--extra-packages "pytest-cov pytest-mock pytest-timeout locust"
echo "✅ Python environment ready"
- name: Run linting
run: |
cd /var/lib/aitbc-workspaces/python-tests/repo
source venv/bin/activate
if command -v ruff >/dev/null 2>&1; then
ruff check apps/ packages/py/ --select E,F --ignore E501 -q || echo "⚠️ Ruff warnings"
fi
echo "✅ Linting completed"
- name: Run tests
run: |
cd /var/lib/aitbc-workspaces/python-tests/repo
source venv/bin/activate
# Install packages in development mode
pip install -e packages/py/aitbc-crypto/
pip install -e packages/py/aitbc-sdk/
export PYTHONPATH="apps/coordinator-api/src:apps/blockchain-node/src:apps/wallet/src:packages/py/aitbc-crypto/src:packages/py/aitbc-sdk/src:."
# Test if packages are importable
python3 -c "import aitbc_crypto; print('✅ aitbc_crypto imported')"
python3 -c "import aitbc_sdk; print('✅ aitbc_sdk imported')"
pytest tests/archived_phase_tests/ \
tests/cross_phase/ \
apps/wallet/tests/ \
packages/py/aitbc-crypto/tests/ \
packages/py/aitbc-sdk/tests/ \
--tb=short -q --timeout=30 --import-mode=importlib
echo "✅ Python tests completed"
- name: Cleanup
if: always()
run: rm -rf /var/lib/aitbc-workspaces/python-tests