BUG: Nightly CI runner python accessed via py#75
Conversation
|
Warning Review limit reached
Next review available in: 36 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
There was a problem hiding this comment.
Pull request overview
Updates the Windows self-hosted nightly health workflow to create the test virtual environment using the Windows Python launcher (py) instead of a hard-coded, user-specific python.exe path.
Changes:
- Switch venv creation from a fixed
C:\Users\...\Python311\python.exepath topy -m venv. - Keep subsequent steps relying on the venv
Scriptsdirectory being added toGITHUB_PATH.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| # Python 3.11 is required because the [physicsnemo] extra pulls in | ||
| # nvidia-physicsnemo, which requires Python >= 3.11. | ||
| run: | | ||
| & "C:\Users\saylward\AppData\Local\Programs\Python\Python311\python.exe" -m venv "$env:RUNNER_TEMP\physiomotion4d-venv" | ||
| & py -m venv "$env:RUNNER_TEMP\physiomotion4d-venv" | ||
| echo "$env:RUNNER_TEMP\physiomotion4d-venv\Scripts" >> $env:GITHUB_PATH |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #75 +/- ##
==========================================
+ Coverage 34.66% 34.68% +0.01%
==========================================
Files 57 57
Lines 7283 7283
==========================================
+ Hits 2525 2526 +1
+ Misses 4758 4757 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
No description provided.