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 1971563 - kitty fails to build in rawhide: ERROR: test_multiprocessing_spawn (kitty_tests.tui.TestTUI)
Summary: kitty fails to build in rawhide: ERROR: test_multiprocessing_spawn (kitty_tes...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kitty
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Artem
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3.10 F35FTBFS, RAWHIDEFTBFS
TreeView+ depends on / blocked
 
Reported: 2021-06-14 10:56 UTC by Miro Hrončok
Modified: 2021-06-14 12:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-14 12:05:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2021-06-14 10:56:02 UTC
Hello.

It appears that kitty-0.21.1-1.fc35 fails to build in rawhide with some test failures on at least s390x:

======================================================================
ERROR: test_multiprocessing_spawn (kitty_tests.tui.TestTUI)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/kitty-0.21.1/kitty_tests/tui.py", line 48, in test_multiprocessing_spawn
    test_spawn()
    self = <kitty_tests.tui.TestTUI testMethod=test_multiprocessing_spawn>
    test_spawn = <function test_spawn at 0x3ffad2fa0e0>
  File "/builddir/build/BUILD/kitty-0.21.1/kitty/multiprocessing.py", line 68, in test_spawn
    x = q.get(timeout=2)
    ctx = <multiprocessing.context.SpawnContext object at 0x3ffae920bb0>
    get_context = <bound method DefaultContext.get_context of <multiprocessing.context.DefaultContext object at 0x3ffae920b80>>
    p = <SpawnProcess name='SpawnProcess-1' pid=2645726 parent=2645715 stopped exitcode=1>
    q = <multiprocessing.queues.Queue object at 0x3ffae3dffa0>
  File "/usr/lib64/python3.10/multiprocessing/queues.py", line 114, in get
    raise Empty
    block = True
    deadline = 663352.157820916
    self = <multiprocessing.queues.Queue object at 0x3ffae3dffa0>
    timeout = 1.999996468075551
_queue.Empty
----------------------------------------------------------------------
Ran 102 tests in 3.145s
FAILED (errors=1, skipped=2)

This blocks the Python 3.10 rebuild of the package.

Comment 1 Miro Hrončok 2021-06-14 10:58:20 UTC
This appears to be a timeout issue. Maybe the builder is just too slow? In copr, the package builds fine: https://copr.fedorainfracloud.org/coprs/g/python/python3.10/package/kitty/

Running 3 scratchbuilds on all architectures to see how relevant the individual architectures are for the failures.

Comment 2 Artem 2021-06-14 11:11:02 UTC
Miro good day. I've in a hurry reported upstream https://github.com/kovidgoyal/kitty/issues/3712
Didn't look into that yet, but seems like there is a two python version installed at the same time.

Comment 3 Miro Hrončok 2021-06-14 11:13:49 UTC
Observations: this happens on all architectures, even if I sed s/timeout=2/timeout=20/.


> seems like there is a two python version installed at the same time.

Indeed python3.9 is installed in root.log. Let me see why.

Comment 4 Miro Hrončok 2021-06-14 11:15:57 UTC
Because of:

    BuildRequires:  kitty

Let's build without tests first, only to build with tests later.

Comment 5 Miro Hrončok 2021-06-14 11:17:55 UTC
Oh no, wait, this is only because https://github.com/kovidgoyal/kitty/issues/2881 to add kitty on PATH. We should not install kitty to add it to PATH, we should add the recently built kitty to it.

Comment 7 Artem 2021-06-14 12:05:10 UTC
Miro thanks a lot for help. Now it built successfully on Rawhide.


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