-
Notifications
You must be signed in to change notification settings - Fork 3.6k
test: addressing flaky spawn "process 0 terminated with signal SIGABRT" #20933
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
⚡ Required checks status: All passing 🟢Groups summary🟢 pytorch_lightning: Tests workflow
These checks are required after the changes to 🟢 pytorch_lightning: Azure GPU
These checks are required after the changes to 🟢 lightning_fabric: CPU workflow
These checks are required after the changes to Thank you for your contribution! 💜
|
890b173
to
66dcf3d
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #20933 +/- ##
========================================
- Coverage 87% 86% -1%
========================================
Files 268 268
Lines 23442 23453 +11
========================================
- Hits 20394 20271 -123
- Misses 3048 3182 +134 |
What does this PR do?
We tried to patch it in #20912, but still happening so let's automate the re-run
Before submitting
PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:
Reviewer checklist
📚 Documentation preview 📚: https://pytorch-lightning--20933.org.readthedocs.build/en/20933/