build(deps): bump pytest-rerunfailures from 16.0.1 to 16.1 in /requirements

[dependabot]

Bumps pytest-rerunfailures from 16.0.1 to 16.1.

Changelog

Sourced from pytest-rerunfailures's changelog.

16.1 (2025-10-10)

• Drop support for Python 3.9.

• Changed "localhost" to "127.0.0.1" to avoid bad hostname resolution.

• Added --force-reruns to override rerun count globally. Fixes [#306](https://github.com/pytest-dev/pytest-rerunfailures/issues/306) <https://github.com/pytest-dev/pytest-rerunfailures/issues/306>_.

Commits

• b015092 Preparing release 16.1
• c1666dd Prepare release.
• 8d04ad9 Fix NotImplementedError crash when using xdist schedulers without `mark_tes...
• cb8ede7 Add a --force-reruns to override rerun count globally (#307)
• 5e01132 Bump actions/setup-python from 5 to 6 in the actions group (#310)
• 88e0023 Drop support for Python 3.9. (#308)
• df47974 Change 'localhost' to '127.0.0.1' (#305)
• f149c7d Back to development: 16.1
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

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

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

🟢 pytorch_lightning: lit GPU

Check ID	Status
pytorch.yml / Lit Job (nvidia/cuda:12.1.1-runtime-ubuntu22.04, pytorch, 3.10)	success	✅
pytorch.yml / Lit Job (lightning, 3.12)	success	✅
pytorch.yml / Lit Job (pytorch, 3.12)	success	✅

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

🟢 Benchmarks

Check ID	Status
benchmark.yml / Lit Job (fabric)	success	✅
benchmark.yml / Lit Job (pytorch)	success	✅

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

🟢 lightning_fabric: lit GPU

Check ID	Status
fabric.yml / Lit Job (nvidia/cuda:12.1.1-runtime-ubuntu22.04, fabric, 3.10)	success	✅
fabric.yml / Lit Job (fabric, 3.12)	success	✅
fabric.yml / Lit Job (lightning, 3.12)	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/test.txt.

🟢 install

Check ID	Status
install-pkg-guardian	success	✅

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

---

Thank you for your contribution! 💜

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87%. Comparing base (851e66f) to head (9a6934a).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff            @@
##           master   #21283    +/-   ##
========================================
- Coverage      87%      87%    -1%     
========================================
  Files         269      269            
  Lines       23690    23690            
========================================
- Hits        20668    20535   -133     
- Misses       3022     3155   +133     

[bhimrazy]

It seems they have dropped support for Python 3.9, so we can probably skip this version update for pytest-rerunfailures since our tests are still running on 3.9.

cc: @ethanwharris @Borda

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[Borda]

You can make it with switch so for Python 3.9 you keep the actual and for later version go with this update...

[bhimrazy]

You can make it with switch so for Python 3.9 you keep the actual and for later version go with this update...

Thanks for the suggestion, @Borda ! I’ll look into it and see how we can incorporate this.