fix: optimize CI tests by separating fast/slow models and reducing parameterization #126
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
CI tests were taking 20+ minutes, making development feedback loops too slow and blocking contributors.
Root Causes
Solution
1. Test Categorization
slowpytest marker for foundation model tests-m 'not live and not slow'2. Parameterization Optimization
3. CI Infrastructure
4. Foundation Model Strategy
Performance Impact
Files Changed
.github/workflows/ci.yaml- Optimized main CI with caching and timeouts.github/workflows/comprehensive.yaml- New nightly workflow for foundation modelstests/conftest.py- Split fast/comprehensive model liststests/models/test_models.py- Reduced parameterization for speedtests/models/test_models_comprehensive.py- Full foundation model coveragetests/test_smoke.py- Fast import validation testsTESTING.md- Developer documentation for new test structureValidation
✅ Fast models cover all core forecasting logic
✅ Foundation models tested comprehensively (nightly)
✅ Import issues caught early (smoke tests)
✅ API integration preserved (live tests)
✅ Model weight caching reduces download overhead
This maintains full test coverage while providing rapid feedback for development.
Fixes #125.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
astral.shcurl -LsSf REDACTED(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.