Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1919795 - hatch fails to build with Python 3.10: AssertionError: timeout
Summary: hatch fails to build with Python 3.10: AssertionError: timeout
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: hatch
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lumír Balhar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1906368
Blocks: PYTHON3.10
TreeView+ depends on / blocked
 
Reported: 2021-01-25 07:58 UTC by Tomáš Hrnčiar
Modified: 2021-03-03 14:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-03 14:41:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tomáš Hrnčiar 2021-01-25 07:58:06 UTC
hatch fails to build with Python 3.10.0a4.

=================================== FAILURES ===================================
______________________________ test_existing_venv ______________________________

    def test_existing_venv():
        with temp_chdir():
            runner = CliRunner()
    
            env_name = get_new_venv_name()
            venv_dir = os.path.join(get_venv_dir(), env_name)
    
            try:
                runner.invoke(hatch, ['env', env_name])
>               wait_until(is_venv, venv_dir)

tests/commands/test_env.py:102: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

f = <function is_venv at 0x7f113d108a60>
args = ('/builddir/.virtualenvs/-5Jq',), end_time = 1611339469.5794718

    def wait_until(f, *args):  # no cov
        # https://github.com/kennethreitz/pipenv/pull/403
        end_time = time.time() + 540
        while time.time() < end_time:
            if f(*args):
                time.sleep(0.5)
                return True
            time.sleep(0.2)
>       raise AssertionError('timeout')
E       AssertionError: timeout

tests/utils.py:29: AssertionError

=========================== short test summary info ============================
FAILED tests/commands/test_env.py::test_existing_venv - AssertionError: timeout
= 1 failed, 273 passed, 64 skipped, 1 deselected, 15 warnings in 618.90s (0:10:18) =

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.10/fedora-rawhide-x86_64/01894101-hatch/

For all our attempts to build hatch with Python 3.10, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.10/package/hatch/

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.10:
https://copr.fedorainfracloud.org/coprs/g/python/python3.10/

Let us know here if you have any questions.

Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10.
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 1 Lumír Balhar 2021-01-25 11:03:12 UTC
This is not related to Python 3.10. I'll try to find a way how to higher the timeout limit or I'll disable the test entirely.

Comment 2 Ben Cotton 2021-02-09 15:42:40 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 3 Lumír Balhar 2021-03-03 14:41:20 UTC
Semver is fixed and hatch builds fine: https://copr.fedorainfracloud.org/coprs/g/python/python3.10/build/2043901/


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