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
Avoid interactions through test artifacts #19821
Conversation
for more information, see https://pre-commit.ci
⚡ Required checks status: All passing 🟢Groups summary🟢 pytorch_lightning: Tests workflowThese checks are required after the changes to 🟢 pytorch_lightning: Azure GPU
These checks are required after the changes to 🟢 lightning_fabric: CPU workflowThese checks are required after the changes to 🟢 lightning_fabric: Azure GPU
These checks are required after the changes to Thank you for your contribution! 💜
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #19821 +/- ##
=========================================
- Coverage 84% 59% -25%
=========================================
Files 424 419 -5
Lines 34698 34600 -98
=========================================
- Hits 29153 20248 -8905
- Misses 5545 14352 +8807 |
for more information, see https://pre-commit.ci
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.
Good idea
What does this PR do?
In #19706 I noticed a test interaction through a checkpoint dir or log dir that was saved to cwd instead of tmp_path (I don't remember which ones). So I decided to write a safety guard against that in conftest.py.
📚 Documentation preview 📚: https://pytorch-lightning--19821.org.readthedocs.build/en/19821/
cc @Borda @carmocca @justusschock @awaelchli