try to fix github cache - #619
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
superseded by #620 |
This PR makes test-data caching deterministic in GitHub Actions.
Previously, DASCore’s test data cache was populated lazily during test execution. Because multiple CI jobs shared the same cache key, whichever job saved first could publish a partial cache. Later jobs would restore
that incomplete cache and still need to download missing files, which made the cache look unreliable.
This change introduces an explicit cache-priming step that downloads the full contents of dascore/data_registry.txt before test jobs run.