Skip to content

bump: try deepspeed >=0.14.1,<=0.15.0 #21076

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

Merged
merged 22 commits into from
Aug 19, 2025
Merged

bump: try deepspeed >=0.14.1,<=0.15.0 #21076

merged 22 commits into from
Aug 19, 2025

Conversation

Borda
Copy link
Member

@Borda Borda commented Aug 15, 2025

What does this PR do?

'Let''s see if we are fine with this bump

Before submitting
  • Was this discussed/agreed via a GitHub issue? (not for typos and docs)
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure your PR does only one thing, instead of bundling different changes together?
  • Did you make sure to update the documentation with your changes? (if necessary)
  • Did you write any new necessary tests? (not for typos and docs)
  • Did you verify new and existing tests pass locally with your changes?
  • Did you list all the breaking changes introduced by this pull request?
  • Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

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
  • Is this pull request ready for review? (if not, please submit in draft mode)
  • Check that all items from Before submitting are resolved
  • Make sure the title is self-explanatory and the description concisely explains the PR
  • Add labels and milestones (and optionally projects) to the PR so it can be classified

📚 Documentation preview 📚: https://pytorch-lightning--21076.org.readthedocs.build/en/21076/

@github-actions github-actions bot added fabric lightning.fabric.Fabric pl Generic label for PyTorch Lightning package dependencies Pull requests that update a dependency file labels Aug 15, 2025
Copy link
Contributor

github-actions bot commented Aug 15, 2025

⚡ Required checks status: All passing 🟢

Groups summary

🟢 pytorch_lightning: Tests workflow
Check ID Status
pl-cpu-guardian success

These checks are required after the changes to .actions/assistant.py, requirements/fabric/strategies.txt, src/lightning/fabric/strategies/deepspeed.py, requirements/pytorch/strategies.txt, tests/tests_pytorch/utilities/test_compile.py, pyproject.toml.

🟢 pytorch_lightning: Azure GPU
Check ID Status
pytorch-lightning (GPUs) (testing Lightning | latest) success
pytorch-lightning (GPUs) (testing PyTorch | oldest) success
pytorch-lightning (GPUs) (testing PyTorch | latest) success

These checks are required after the changes to .actions/assistant.py, .azure/gpu-tests-pytorch.yml, requirements/pytorch/strategies.txt, tests/tests_pytorch/utilities/test_compile.py, pyproject.toml, requirements/fabric/strategies.txt, src/lightning/fabric/strategies/deepspeed.py.

🟢 pytorch_lightning: Benchmarks
Check ID Status
lightning.Benchmarks success

These checks are required after the changes to requirements/fabric/strategies.txt, requirements/pytorch/strategies.txt, src/lightning/fabric/strategies/deepspeed.py.

🟢 fabric: Docs
Check ID Status
docs-make (fabric, doctest) success
docs-make (fabric, html) success

These checks are required after the changes to src/lightning/fabric/strategies/deepspeed.py, requirements/fabric/strategies.txt, pyproject.toml.

🟢 pytorch_lightning: Docs
Check ID Status
docs-make (pytorch, doctest) success
docs-make (pytorch, html) success

These checks are required after the changes to .actions/assistant.py, requirements/pytorch/strategies.txt, pyproject.toml.

🟢 pytorch_lightning: Docker
Check ID Status
build-cuda (3.10, 2.1.2, 12.1.1) success
build-cuda (3.11, 2.2.2, 12.1.1) success
build-cuda (3.11, 2.3.1, 12.1.1) success
build-cuda (3.11, 2.4.1, 12.1.1) success
build-cuda (3.12, 2.5.1, 12.1.1) success
build-cuda (3.12, 2.6.0, 12.4.1) success
build-pl (3.10, 2.1, 12.1.1) success
build-pl (3.11, 2.2, 12.1.1) success
build-pl (3.11, 2.3, 12.1.1) success
build-pl (3.11, 2.4, 12.1.1) success
build-pl (3.12, 2.5, 12.1.1) success
build-pl (3.12, 2.6, 12.4.1) success
build-pl (3.12, 2.7, 12.6.3) success
build-pl (3.12, 2.8, 12.6.3, true) success

These checks are required after the changes to .actions/assistant.py, dockers/release/Dockerfile, requirements/pytorch/strategies.txt, requirements/fabric/strategies.txt.

🟢 lightning_fabric: CPU workflow
Check ID Status
fabric-cpu-guardian success

These checks are required after the changes to .actions/assistant.py, requirements/fabric/strategies.txt, src/lightning/fabric/strategies/deepspeed.py, tests/tests_fabric/strategies/launchers/test_multiprocessing_integration.py, pyproject.toml.

🟢 lightning_fabric: Azure GPU
Check ID Status
lightning-fabric (GPUs) (testing Fabric | oldest) success
lightning-fabric (GPUs) (testing Fabric | latest) success
lightning-fabric (GPUs) (testing Lightning | latest) success

These checks are required after the changes to .actions/assistant.py, .azure/gpu-tests-fabric.yml, requirements/fabric/strategies.txt, src/lightning/fabric/strategies/deepspeed.py, tests/tests_fabric/strategies/launchers/test_multiprocessing_integration.py, pyproject.toml.

🟢 mypy
Check ID Status
mypy success

These checks are required after the changes to .actions/assistant.py, requirements/fabric/strategies.txt, requirements/pytorch/strategies.txt, src/lightning/fabric/strategies/deepspeed.py, pyproject.toml.

🟢 install
Check ID Status
install-pkg-guardian success

These checks are required after the changes to .actions/assistant.py, src/lightning/fabric/strategies/deepspeed.py, requirements/fabric/strategies.txt, requirements/pytorch/strategies.txt.


Thank you for your contribution! 💜

Note
This comment is automatically generated and updates for 60 minutes every 180 seconds. If you have any other questions, contact carmocca for help.

Copy link

codecov bot commented Aug 15, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87%. Comparing base (8ff43d4) to head (47167b6).
⚠️ Report is 1 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #21076   +/-   ##
=======================================
  Coverage      87%      87%           
=======================================
  Files         269      269           
  Lines       23509    23506    -3     
=======================================
- Hits        20494    20492    -2     
+ Misses       3015     3014    -1     

@github-actions github-actions bot added the ci Continuous Integration label Aug 15, 2025
@Borda
Copy link
Member Author

Borda commented Aug 15, 2025

This seems a bit unrelated:

FAILED strategies/launchers/test_multiprocessing_integration.py::test_memory_sharing_disabled[ddp_fork] - torch.multiprocessing.spawn.ProcessRaisedException: 

-- Process 0 terminated with the following error:
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/torch/multiprocessing/spawn.py", line 90, in _wrap
    fn(i, *args)
  File "/Users/runner/work/pytorch-lightning/pytorch-lightning/src/lightning_fabric/strategies/launchers/multiprocessing.py", line 142, in _wrapping_function
    results = function(*args, **kwargs)
              ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/runner/work/pytorch-lightning/pytorch-lightning/src/lightning_fabric/fabric.py", line 934, in _wrap_with_setup
    return to_run(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/runner/work/pytorch-lightning/pytorch-lightning/tests/tests_fabric/strategies/launchers/test_multiprocessing_integration.py", line 58, in _test_memory_sharing_disabled
    fabric.barrier()
  File "/Users/runner/work/pytorch-lightning/pytorch-lightning/src/lightning_fabric/fabric.py", line 547, in barrier
    self._strategy.barrier(name=name)
  File "/Users/runner/work/pytorch-lightning/pytorch-lightning/src/lightning_fabric/strategies/ddp.py", line 162, in barrier
    torch.distributed.barrier()
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/torch/distributed/c10d_logger.py", line 81, in wrapper
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/torch/distributed/distributed_c10d.py", line 4792, in barrier
    device = torch._C._get_accelerator()
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
RuntimeError: Please register PrivateUse1HooksInterface by `RegisterPrivateUse1HooksInterface` first.

@@ -5,5 +5,5 @@

# note: is a bug around 0.10 with `MPS_Accelerator must implement all abstract methods`
# shall be resolved by https://github.com/microsoft/DeepSpeed/issues/4372
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not for this PR, but this was resolved, so maybe we can relax in the future

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I will continue in relaxing. I just wanted to do it in smaller steps so it's safer to land...

@Borda Borda merged commit ad54bc1 into master Aug 19, 2025
187 of 192 checks passed
@Borda Borda deleted the bump/deepspeed branch August 19, 2025 13:13
matsumotosan pushed a commit to matsumotosan/pytorch-lightning that referenced this pull request Aug 19, 2025
* try `deepspeed >=0.14.1,<=0.15.0`
* drop from oldest
* pip uninstall -y deepspeed
* error::DeprecationWarning
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Continuous Integration dependencies Pull requests that update a dependency file dockers fabric lightning.fabric.Fabric package pl Generic label for PyTorch Lightning package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants