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
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