-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Remove DataLoader serialization (under fault tolerance) #16533
Remove DataLoader serialization (under fault tolerance) #16533
Conversation
⚡ 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 🟢 pytorch_lightning: Azure HPU
These checks are required after the changes to 🟢 pytorch_lightning: Azure IPU
These checks are required after the changes to 🟢 pytorch_lightning: Docs
These checks are required after the changes to 🟢 mypy
These checks are required after the changes to 🟢 installThese checks are required after the changes to 🟢 link-check
These checks are required after the changes to Thank you for your contribution! 💜
|
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.
The change in CI looks good to me!
What does this PR do?
Fault-tolerance is composed of several items:
FaultToleranceCheckpoint
callback opt-in #16512)This PR removes (1) and (2). Parts of this might re-land in the future
This is the last of the fault-tolerance items.
Does your PR introduce any breaking changes? If yes, please list them.
Removes support for serializing the DataLoader state under the
PL_FAULT_TOLERANCE_TRAINING
environment variablecc @carmocca @akihironitta @Borda @justusschock @awaelchli