What?
A weekly automated process to identify and track the slowest tests in the conda test suite for review and optimization.
Why?
- Slow tests impact CI turnaround time and developer productivity
- No systematic process exists to identify and address slow tests
- Test duration creep happens gradually without visibility
- Some slow tests may indicate underlying code issues worth investigating
User impact
- Faster CI feedback loops for contributors
- Reduced resource consumption on CI runners
- Better test suite maintainability
Goals
What?
A weekly automated process to identify and track the slowest tests in the conda test suite for review and optimization.
Why?
User impact
Goals