6 Commits

Author	SHA1	Message	Date
aitbc1	8d6a05f09c	fix: resolve YAML indentation issues in Python debugging script ... YAML INDENTATION FIX: Use single-line Python commands to avoid indentation Issue: - IndentationError persists due to YAML multi-line string handling - Multi-line Python strings in YAML cause indentation conflicts - Workflow still failing with syntax errors Solution: - Use single-line Python commands with exec() - Escape newlines with \n in exec() strings - Separate commands for each import test - Avoid YAML multi-line string indentation issues Changes: - Single-line venv/bin/python -c commands - exec() with escaped newlines for try/except blocks - Separate commands for src and aitbc imports - Maintains debugging functionality without YAML conflicts Expected results: - No more IndentationError - Import debugging should work - Workflow should continue to pytest execution - Clear feedback on import success/failure This should finally resolve the YAML/Python indentation conflict and allow the workflow to proceed to actual test execution.	2026-03-27 20:48:18 +01:00
aitbc1	536f7afbcc	fix: correct indentation error in Python debugging script ... INDENTATION FIX: Resolve Python syntax error in import debugging Issue: - IndentationError: unexpected indent in Python debugging script - Caused workflow to fail with exit status 1 - Blocked test execution entirely Fix: - Corrected Python script indentation - Moved import sys to top level - Proper try/except block structure - Clean f-string formatting Expected results: - No more IndentationError - Import debugging should work - Test execution should proceed - Clear feedback on import success/failure This should allow the workflow to continue past the debugging section and actually run the pytest tests.	2026-03-27 20:46:50 +01:00
aitbc1	4464ab05f4	fix: add database setup and resolve final import issues ... FINAL IMPORT FIX: Database setup and remaining dependency issues Progress achieved: - Before: collected 0 items / 5 errors - After: collected 61 items / 5 errors (MAJOR IMPROVEMENT!) Remaining issues addressed: 1. Missing 'requests' dependency - added 2. Database file errors - created database directories and files 3. Persistent import issues - added import debugging and path fixes New features: - Database setup: Create mempool.db files in multiple locations - Import debugging: Test specific imports that were failing - Increased maxfail: 10 errors before stopping (from 5) - Better error handling: More comprehensive debugging Database setup: - mkdir -p data/blockchain and apps/blockchain-node/data - touch mempool.db files to prevent sqlite3 errors - Multiple locations to cover different test configurations Import debugging: - Test src.message_protocol import directly - Test aitbc_chain import directly - Add sys.path.insert for problematic imports - Clear success/failure feedback Expected results: - requests import error resolved - Database file errors resolved - Better import resolution for remaining issues - More tests should run successfully - Clear debugging output for troubleshooting This should resolve the final 5 errors and allow more of the 61 collected tests to run successfully.	2026-03-27 20:45:50 +01:00
aitbc1	6c7b56e086	fix: add missing dependencies and improve import path resolution ... IMPORT FIX: Add sqlmodel and comprehensive PYTHONPATH setup Issues identified from test run: - ModuleNotFoundError: No module named 'sqlmodel' - ModuleNotFoundError: No module named 'src' (agent-protocols) - ModuleNotFoundError: No module named 'aitbc' (blockchain-node) Solutions applied: 1. Add missing dependencies: - sqlmodel (for blockchain-node database) - sqlalchemy (for sqlmodel dependency) 2. Improve PYTHONPATH with specific paths: - /opt/gitea-runner/workspace/repo/apps/agent-protocols/src - /opt/gitea-runner/workspace/repo/apps/blockchain-node/src - /opt/gitea-runner/workspace/repo/apps/coordinator-api/src - /opt/gitea-runner/workspace/repo/cli - /opt/gitea-runner/workspace/repo/packages/py/aitbc-crypto/src - /opt/gitea-runner/workspace/repo/packages/py/aitbc-sdk/src 3. Applied to both jobs (test and test-specific) Expected results: - sqlmodel import errors resolved - src imports resolved for agent-protocols - aitbc imports resolved for blockchain-node - Better import resolution across all apps - More tests should be able to run successfully This addresses the specific import errors seen in the test run and provides comprehensive import path coverage for the complex project structure.	2026-03-27 20:43:27 +01:00
aitbc1	671066a6f5	fix: use --no-root in python-tests to avoid package installation issues ... PYTHON-TESTS FIX: Avoid package installation errors Issue: Poetry install failing with 'No file/folder found for package aitbc-cli' Root cause: Complex setuptools package configuration in pyproject.toml Problem: Project configured as package but with complex multi-source structure Solution: Use --no-root flag like other workflows Changes: - install --no-root (both jobs) - Skip current project installation - Install only dependencies from poetry.lock - Maintain all other test functionality Benefits: - Avoids package installation complexity - Consistent with other workflows - Focus on dependency installation for testing - Clean separation of concerns This fixes the poetry installation failure while maintaining comprehensive test environment setup for import resolution.	2026-03-27 20:40:17 +01:00
aitbc1	cd34180e64	feat: create dedicated python-tests workflow for comprehensive testing ... DEDICATED TEST WORKFLOW: Separate testing from main CI Creates python-tests.yml with comprehensive test handling: Features: - Separate workflow from main CI (keeps CI clean) - Comprehensive Python path setup for import resolution - Install ALL dependencies with poetry (not --no-root) - Additional dependencies: pydantic-settings, pytest-cov, pytest-mock - Multiple PYTHONPATH entries for complex project structure - Two jobs: general tests + specific tests (manual trigger) Import Error Handling: - Full project installation (poetry install) - Multiple Python path entries: - /opt/gitea-runner/workspace/repo - /opt/gitea-runner/workspace/repo/src - /opt/gitea-runner/workspace/repo/apps - /opt/gitea-runner/workspace/repo/apps/*/src - Missing dependencies: pydantic-settings - Error tolerance: --maxfail=5, --tb=short Benefits: - Main CI stays clean and fast - Tests can fail without blocking CI - Comprehensive test environment setup - Manual trigger for specific test debugging - Better import resolution for complex project structure This separates concerns: CI focuses on build/deployment, while this workflow focuses on comprehensive testing.	2026-03-27 20:23:23 +01:00