kitty ftbfs due to crypto test failure "Cannot allocate memory" on ppc64el

Bug #2004435 reported by Bryce Harrington
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KittyOS
Unknown
Unknown
kitty (Debian)
Fix Released
Unknown
kitty (Ubuntu)
Fix Released
Undecided
Olivier Gayot

Bug Description

ERROR: test_elliptic_curve_data_exchange (kitty_tests.crypto.TestCrypto.test_elliptic_curve_data_exchange)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/<<PKGBUILDDIR>>/kitty/launcher/../../kitty_tests/crypto.py", line 18, in test_elliptic_curve_data_exchange
    alice_secret = alice.derive_secret(bob.public)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    AES256GCMDecrypt = <class 'fast_data_types.AES256GCMDecrypt'>
    AES256GCMEncrypt = <class 'fast_data_types.AES256GCMEncrypt'>
    CryptoError = <class 'fast_data_types.CryptoError'>
    EllipticCurveKey = <class 'fast_data_types.EllipticCurveKey'>
    alice = <fast_data_types.EllipticCurveKey object at 0x78545f9f9990>
    bob = <fast_data_types.EllipticCurveKey object at 0x78545f9f9b90>
    self = <kitty_tests.crypto.TestCrypto testMethod=test_elliptic_curve_data_exchange>
OSError: [Errno 12] Cannot allocate memory

This looks like a possibly matching upstream bug report, with some diagnostic ideas:
  https://github.com/kovidgoyal/kitty/issues/5466

This is blocking the python3-defaults 3.11 transition. Given it's a known issue upstream without a solution, it may be most expedient to simply disable the crypto test case for now?

Revision history for this message
Bryce Harrington (bryce) wrote :

Note there's also a new upstream release 0.27.0, however I saw nothing in that release's changelog to suggest it includes a fix for this issue.

tags: added: update-excuse
Olivier Gayot (ogayot)
Changed in kitty (Ubuntu):
assignee: nobody → Olivier Gayot (ogayot)
Olivier Gayot (ogayot)
Changed in kitty (Ubuntu):
status: New → In Progress
Revision history for this message
Olivier Gayot (ogayot) wrote :

Adding patch to disable the test if RLIMIT_MEMLOCK is too low

Revision history for this message
Olivier Gayot (ogayot) wrote :

Successful ppc64el build on PPA: https://launchpad.net/~ogayot/+archive/ubuntu/lunar-proposed/+build/25540132

test_elliptic_curve_data_exchange (kitty_tests.crypto.TestCrypto.test_elliptic_curve_data_exchange) ... skipped 'RLIMIT_MEMLOCK is too low'

Successful amd64 build on PPA: https://launchpad.net/~ogayot/+archive/ubuntu/lunar-proposed/+build/25540131

test_elliptic_curve_data_exchange (kitty_tests.crypto.TestCrypto.test_elliptic_curve_data_exchange) ... ok

Changed in kitty (Ubuntu):
status: In Progress → New
Revision history for this message
Simon Quigley (tsimonq2) wrote :

🐱 ➡️ 🚀

Jeremy Bícha (jbicha)
Changed in kitty (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kitty - 0.26.5-3ubuntu2

---------------
kitty (0.26.5-3ubuntu2) lunar; urgency=medium

  * disable crypto test if RLIMIT_MEMLOCK is too low (LP: #2004435)

 -- Olivier Gayot <email address hidden> Wed, 01 Feb 2023 12:31:03 +0100

Changed in kitty (Ubuntu):
status: Fix Committed → Fix Released
Changed in kitty (Debian):
status: Unknown → New
Revision history for this message
Olivier Gayot (ogayot) wrote :
Changed in kitty (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.