ci: add explicit venv cleanup before setup in all workflows to prevent cache corruption
Some checks failed
API Endpoint Tests / test-api-endpoints (push) Successful in 10s
CLI Tests / test-cli (push) Failing after 41s
Integration Tests / test-service-integration (push) Successful in 2m10s
Package Tests / Python package - aitbc-agent-sdk (push) Failing after 4s
Package Tests / Python package - aitbc-core (push) Failing after 4s
Package Tests / Python package - aitbc-crypto (push) Failing after 5s
Package Tests / Python package - aitbc-sdk (push) Failing after 4s
Package Tests / JavaScript package - aitbc-sdk-js (push) Failing after 16m15s
Production Tests / Production Integration Tests (push) Failing after 7s
Python Tests / test-python (push) Failing after 1m33s
Security Scanning / security-scan (push) Failing after 3s
Staking Tests / test-staking-service (push) Failing after 2m21s
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
Package Tests / JavaScript package - aitbc-token (push) Failing after 12m54s

Added `rm -rf venv` (and `venv-build` where applicable) before venv setup in all CI workflows to ensure clean installations and prevent cache corruption issues. Removed redundant venv corruption detection and rebuild logic from package-tests.yml since explicit cleanup makes it unnecessary.
This commit is contained in:
aitbc
2026-04-20 06:10:32 +02:00
parent 05b3b02166
commit ffb1f2a4f8
8 changed files with 37 additions and 31 deletions

View File

@@ -35,7 +35,10 @@ jobs:
- name: Setup Python environment
run: |
cd /var/lib/aitbc-workspaces/staking-tests/repo
# Remove any existing venv to avoid cache corruption issues
rm -rf venv
bash scripts/ci/setup-python-venv.sh \
--repo-dir "$PWD" \
--venv-dir "$PWD/venv"