-
Notifications
You must be signed in to change notification settings - Fork 45
Fix document warnings related CI infrastructure #2148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #2148 +/- ##
=========================================
Coverage 84.89% 84.90%
=========================================
Files 1273 1273
Lines 44667 44667
Branches 16765 16611 -154
=========================================
+ Hits 37922 37924 +2
+ Misses 4933 4758 -175
- Partials 1812 1985 +173 🚀 New features to boost your workflow:
|
Test summary 5 726 files 9 212 suites 17m 56s ⏱️ Results for commit 2b62f87. ♻️ This comment has been updated with latest results. |
…disable device debug" This reverts commit 3b81610. We've got vecgeom built against 70, and it seems that the build time increased drastically as a result of that or virtual. Testing independently, it seems there is little to no difference for omitting the real architecture.
Why is it now unnecessary? (The linked issue is not explicitly marked resolved). |
|
@pcanal The issue I posted was primarily because of a bug in Git that was present for one minor patch version that seems to have been quickly fixed and deployed to the latest github runners. |
pcanal
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Warnings in the sphinx documentation were accidentally disabled in (I think) #1988 because warnings are now shown during doctree generation rather than html construction. I fixed the couple errors in the docs that have accumulated during that time.
Related, I've removed a now-unnecessary workaround for actions/checkout#2041 , and I've added code to get the build size and clean the build directory after it's last used, since we now seem to see intermittent failures on the CUDA builds https://github.com/celeritas-project/celeritas/actions/runs/19948559972/job/57204118695 .
To fix the size overrun errors (nearly 5GB for the debug/reldeb) I've disabled CUBIN compilation for the reldeb case and turned off DEVICE_DEBUG for the debug case.