ci: pin also test requirements for minimal setup

[Borda]

What does this PR do?

this shall resolve unexpected breaking with deepseed and oldest versions
see for example: https://github.com/Lightning-AI/pytorch-lightning/actions/runs/17076057438/job/48417661237

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--21102.org.readthedocs.build/en/21102/

[github-actions]

⚡ 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 .github/workflows/ci-tests-pytorch.yml, requirements/fabric/test.txt, requirements/pytorch/loggers.info, requirements/pytorch/test.txt.

🟢 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 requirements/pytorch/loggers.info, requirements/pytorch/test.txt, requirements/fabric/test.txt.

🟢 pytorch_lightning: Benchmarks

Check ID	Status
lightning.Benchmarks	success	✅

These checks are required after the changes to requirements/fabric/test.txt, requirements/pytorch/loggers.info, requirements/pytorch/test.txt.

🟢 fabric: Docs

Check ID	Status
docs-make (fabric, doctest)	success	✅
docs-make (fabric, html)	success	✅

These checks are required after the changes to requirements/fabric/test.txt.

🟢 pytorch_lightning: Docs

Check ID	Status
docs-make (pytorch, doctest)	success	✅
docs-make (pytorch, html)	success	✅

These checks are required after the changes to requirements/pytorch/loggers.info, requirements/pytorch/test.txt.

🟢 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 requirements/pytorch/loggers.info, requirements/pytorch/test.txt, requirements/fabric/test.txt.

🟢 lightning_fabric: CPU workflow

Check ID	Status
fabric-cpu-guardian	success	✅

These checks are required after the changes to requirements/fabric/test.txt, .github/workflows/ci-tests-fabric.yml.

🟢 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 requirements/fabric/test.txt.

🟢 mypy

Check ID	Status
mypy	success	✅

These checks are required after the changes to requirements/fabric/test.txt, requirements/pytorch/loggers.info, requirements/pytorch/test.txt.

🟢 install

Check ID	Status
install-pkg-guardian	success	✅

These checks are required after the changes to requirements/fabric/test.txt, requirements/pytorch/loggers.info, requirements/pytorch/test.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.

[Copilot]

Pull Request Overview

This PR updates CI workflows to pin test requirements for minimal setup configurations to resolve unexpected breaking changes with DeepSpeed and oldest supported versions. The changes ensure that test dependencies are also pinned to their oldest compatible versions during CI testing.

• Added 'test.txt' to the requirements files list for oldest version pinning in both PyTorch and Fabric workflows
• Reformatted pip install commands for better readability by splitting long lines

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/ci-tests-pytorch.yml	Added 'test.txt' to oldest requirements pinning and reformatted pip install command
.github/workflows/ci-tests-fabric.yml	Added 'test.txt' and 'examples.txt' to oldest requirements pinning and reformatted pip install command

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87%. Comparing base (ff64a92) to head (74911d8).
⚠️ Report is 4 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #21102   +/-   ##
=======================================
  Coverage      87%      87%           
=======================================
  Files         269      269           
  Lines       23514    23514           
=======================================
+ Hits        20500    20503    +3     
+ Misses       3014     3011    -3     

[Borda]

fitting issues with tensorboardX as

E     TypeError: Descriptors cannot be created directly.
E     If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
E     If you cannot immediately regenerate your protos, some other possible workarounds are:
E      1. Downgrade the protobuf package to 3.20.x or lower.
E      2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).
E     
E     More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates