Bug 2325181 - python-APScheduler fails to build with Python 3.14: AssertionError: assert None == 'test' where None = <JobExecutionEvent (code=16384)>.retval
Summary: python-APScheduler fails to build with Python 3.14: AssertionError: assert No...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-APScheduler
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: mmassari
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3.14
TreeView+ depends on / blocked
 
Reported: 2024-11-11 13:43 UTC by Karolina Surma
Modified: 2024-11-18 11:54 UTC (History)
3 users (show)

Fixed In Version: 3.10.4-12
Clone Of:
Environment:
Last Closed: 2024-11-18 11:54:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Karolina Surma 2024-11-11 13:43:42 UTC
python-APScheduler fails to build with Python 3.14.0a1.

_______________________ test_max_instances[processpool] ________________________
tests/test_executors.py:70: in test_max_instances
    assert events[0].retval == 'test'
E   AssertionError: assert None == 'test'
E    +  where None = <JobExecutionEvent (code=16384)>.retval
----------------------------- Captured stderr call -----------------------------
Run time of job "nämé (trigger: date[2011-04-03 18:40:00 CEST], paused)" was missed by 4958 days, 18:29:16.620548
Run time of job "nämé (trigger: date[2011-04-03 18:40:00 CEST], paused)" was missed by 4958 days, 18:29:16.630809
____________________ test_submit_job[processpool-executed] _____________________
tests/test_executors.py:95: in test_submit_job
    assert event.code == event_code
E   assert 16384 == 4096
E    +  where 16384 = <JobExecutionEvent (code=16384)>.code
----------------------------- Captured stderr call -----------------------------
Run time of job "nämé (trigger: date[2011-04-03 18:40:00 CEST], paused)" was missed by 4958 days, 18:29:16.813488
______________________ test_submit_job[processpool-error] ______________________
tests/test_executors.py:95: in test_submit_job
    assert event.code == event_code
E   assert 16384 == 8192
E    +  where 16384 = <JobExecutionEvent (code=16384)>.code
----------------------------- Captured stderr call -----------------------------
Run time of job "nämé (trigger: date[2011-04-03 18:40:00 CEST], paused)" was missed by 4958 days, 18:29:17.140313
_______________________________ test_broken_pool _______________________________
tests/test_executors.py:176: in test_broken_pool
    assert pid[0] != killed_pid
E   assert 649 != 649
------------------------------ Captured log call -------------------------------
ERROR    apscheduler.executors.default:base.py:100 Error running job 99f21d3838ee4fdc987eae5fe4b72d0a
concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending.

https://docs.python.org/3.14/whatsnew/3.14.html

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.14/fedora-rawhide-x86_64/08189177-python-APScheduler/

For all our attempts to build python-APScheduler with Python 3.14, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/python-APScheduler/

Testing and mass rebuild of packages is happening in copr.
You can follow these instructions to test locally in mock if your package builds with Python 3.14:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/

Let us know here if you have any questions.

Python 3.14 is planned to be included in Fedora 43.
To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.14.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires),
so if this package is required a lot, it's important for us to get it fixed soon.

We'd appreciate help from the people who know this package best,
but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 2 Miro Hrončok 2024-11-18 11:54:14 UTC
Thanks.


Note You need to log in before you can comment on or make changes to this bug.