CI: Measure complete PR workflow timing - #24007
Conversation
|
/ok to test |
@vyasr, there was an error processing your request: See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/1/ |
|
/ok to test |
@vyasr, there was an error processing your request: See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/1/ |
|
/ok to test |
@vyasr, there was an error processing your request: See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/1/ |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 10 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe PR workflow maps changed files to component-specific C++ and Python test suites. Test scripts use environment flags to skip unaffected suites. Pandas tests use three shards, and temporary timing markers were added. ChangesComponent-specific test selection
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to This change adds CI timing markers, splits CI test selection by component, and increases Pandas test sharding to three. No concrete merge-blocking risk is identified in the supplied current-head evidence. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/ok to test 5a3d137 |
|
/ok to test 5bb3d3a |
|
/ok to test c6af384 |
|
/ok to test c6af384 |
|
/ok to test d8b3714 |
|
/ok to test 9393024 |
|
/ok to test 9393024 |
Description
Temporary comment-only markers that intentionally exercise every path-filtered PR job. This draft PR exists solely to collect a current complete-workflow timing baseline; it has no functional effect.
Checklist