Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.71%. Comparing base (7c75fa7) to head (9b23f01).
⚠️ Report is 74 commits behind head on main.

@@           Coverage Diff           @@
##             main    #9891   +/-   ##
=======================================
  Coverage   78.71%   78.71%           
=======================================
  Files         153      153           
  Lines       19258    19258           
  Branches     2561     2561           
=======================================
  Hits        15158    15158           
  Misses       3803     3803           
  Partials      297      297           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

there is already a PR for this #9798

Closing in favor of #9798.
* #9798

Reopening because #9798 uses slanted quotes that prevent Python 3.14 from being found and installed. That pull request tells us nothing about why Python 3.14 fails because Python 3.14 is never installed.

The failing job is caused by an AttributeError: module 'subprocess' has no attribute '_USE_VFORK' when running tests with Python 3.14. This is happening in billiard/compat.py at line 196, where it accesses subprocess._USE_VFORK. In Python 3.14, this private attribute has been removed.

Some of those integration and smoke tests fail on Python 3.14 because of:

• GitHub Actions: Test on Python 3.14 release candidate 2 #9891 (comment)
  • Caused by subprocess._USE_VFORK doesn't change usage of vfork python/cpython#121381
  • Fixed in GitHub Actions: Test on Python 3.14 release candidate 2 billiard#428 ?

Some of those integration and smoke tests fail on Python 3.14 because of:

• GitHub Actions: Test on Python 3.14 release candidate 2 #9891 (comment)

  • Caused by subprocess._USE_VFORK doesn't change usage of vfork python/cpython#121381
  • Fixed in GitHub Actions: Test on Python 3.14 release candidate 2 billiard#428 ?

Ok then let's go forward with this and close the debt once the other issues are finalized.

Thank you!

OK... Py3.14 will still fail some integration tests until a new billiard release is pushed to PyPI.

just to be cautious, we should wait to declare python 3.14 support in celery v5.6 release

I am good with that.

• release a new https://github.com/celery/billiard to PyPI
• release a new https://github.com/celery/librabbitmq to PyPI

I am good with that.

• release a new https://github.com/celery/billiard to PyPI
• release a new https://github.com/celery/librabbitmq to PyPI

https://github.com/celery/billiard/releases/tag/v4.2.2

• release a new https://github.com/celery/librabbitmq to PyPI

The last official release was in 2018:

• https://pypi.org/project/librabbitmq/#history
• https://github.com/celery/librabbitmq/releases/tag/2.0.0

Is this a hard-blocker @cclauss ?

librabbitmq is not a suggested package for new projects, but we can release a new version no problem.