==> Building on luxio ==> Checking for remote environment... ==> Syncing package to remote host... sending incremental file list ./ .SRCINFO 996 100% 0.00kB/s 0:00:00 996 100% 0.00kB/s 0:00:00 (xfr#1, to-chk=5/7) .nvchecker.toml 62 100% 60.55kB/s 0:00:00 62 100% 60.55kB/s 0:00:00 (xfr#2, to-chk=4/7) PKGBUILD 2,043 100% 1.95MB/s 0:00:00 2,043 100% 1.95MB/s 0:00:00 (xfr#3, to-chk=3/7) python-pkcs11_mark-tests-as-xfail.patch 700 21% 683.59kB/s 0:00:00 3,257 100% 3.11MB/s 0:00:00 (xfr#4, to-chk=2/7) python-python-pkcs11-0.7.0-9.log 602 100% 587.89kB/s 0:00:00 602 100% 587.89kB/s 0:00:00 (xfr#5, to-chk=1/7) use-functools-cached-property.patch 966 100% 943.36kB/s 0:00:00 966 100% 943.36kB/s 0:00:00 (xfr#6, to-chk=0/7) sent 2,758 bytes received 181 bytes 1,959.33 bytes/sec total size is 7,516 speedup is 2.56 ==> Patching arch to riscv64... ==> Running extra-riscv64-build -- -d /home/felix/packages/riscv64-pkg-cache:/var/cache/pacman/pkg -l root26 on remote host... ]2;🔵 Container arch-nspawn-3792690 on luxio.felixc.at\[?25l:: Synchronizing package databases... core downloading... extra downloading... error: restricting filesystem access failed because landlock is not supported by the kernel! :: Starting full system upgrade... there is nothing to do [?25h==> Building in chroot for [extra] (riscv64)... ==> Synchronizing chroot copy [/var/lib/archbuild/extra-riscv64/root] -> [root26]...done ==> Making package: python-python-pkcs11 0.7.0-9 (Sat Dec 28 20:39:25 2024) ==> Retrieving sources...  -> Found python-pkcs11-0.7.0.tar.gz  -> Found python-pkcs11_mark-tests-as-xfail.patch  -> Found use-functools-cached-property.patch ==> Validating source files with sha256sums... python-pkcs11-0.7.0.tar.gz ... Passed python-pkcs11_mark-tests-as-xfail.patch ... Passed use-functools-cached-property.patch ... Passed ]2;🔵 Container arch-nspawn-3793767 on luxio.felixc.at\==> Making package: python-python-pkcs11 0.7.0-9 (Sat Dec 28 19:39:38 2024) ==> Checking runtime dependencies... ==> Installing missing dependencies... [?25lresolving dependencies... looking for conflicting packages... Package (3) New Version Net Change Download Size extra/mpdecimal 4.0.0-2 0.29 MiB core/python 3.13.1-1 108.57 MiB extra/python-asn1crypto 1.5.1-5 1.49 MiB 0.21 MiB Total Download Size: 0.21 MiB Total Installed Size: 110.35 MiB :: Proceed with installation? [Y/n] :: Retrieving packages... python-asn1crypto-1.5.1-5-any downloading... error: restricting filesystem access failed because landlock is not supported by the kernel! checking keyring... checking package integrity... loading package files... checking for file conflicts... :: Processing package changes... installing mpdecimal... installing python... Optional dependencies for python python-setuptools: for building Python packages using tooling that is usually bundled with Python python-pip: for installing Python packages using tooling that is usually bundled with Python python-pipx: for installing Python software not packaged on Arch Linux sqlite: for a default database integration [installed] xz: for lzma [installed] tk: for tkinter installing python-asn1crypto... :: Running post-transaction hooks... (1/1) Arming ConditionNeedsUpdate... [?25h==> Checking buildtime dependencies... ==> Installing missing dependencies... [?25lresolving dependencies... looking for conflicting packages... Package (24) New Version Net Change Download Size extra/botan 3.6.1-2 9.89 MiB 3.13 MiB extra/python-autocommand 2.2.2-7 0.08 MiB extra/python-cffi 1.17.1-2 1.35 MiB extra/python-iniconfig 2.0.0-6 0.04 MiB extra/python-jaraco.collections 5.0.1-2 0.10 MiB extra/python-jaraco.context 5.3.0-3 0.04 MiB extra/python-jaraco.functools 4.1.0-1 0.07 MiB extra/python-jaraco.text 4.0.0-2 0.08 MiB extra/python-more-itertools 10.5.0-1 0.64 MiB extra/python-packaging 24.2-3 0.66 MiB extra/python-platformdirs 4.3.6-2 0.24 MiB extra/python-pluggy 1.5.0-3 0.20 MiB extra/python-pycparser 2.22-3 1.69 MiB extra/python-pyproject-hooks 1.2.0-3 0.10 MiB extra/cython 3.0.11-2.1 17.12 MiB 3.60 MiB extra/python-build 1.2.2-3 0.20 MiB extra/python-cryptography 44.0.0-1 5.12 MiB extra/python-installer 0.7.0-10 0.17 MiB extra/python-oscrypto 1.3.0-7 2.62 MiB 0.31 MiB extra/python-pytest 1:8.3.4-1 3.92 MiB extra/python-setuptools 1:75.2.0-4 8.05 MiB extra/python-setuptools-scm 8.1.0-3 0.37 MiB extra/python-wheel 0.45.0-3 0.28 MiB extra/softhsm 2.6.1-5 1.25 MiB 0.38 MiB Total Download Size: 7.42 MiB Total Installed Size: 54.28 MiB :: Proceed with installation? [Y/n] :: Retrieving packages... cython-3.0.11-2.1-riscv64 downloading... botan-3.6.1-2-riscv64 downloading... softhsm-2.6.1-5-riscv64 downloading... python-oscrypto-1.3.0-7-any downloading... error: restricting filesystem access failed because landlock is not supported by the kernel! checking keyring... checking package integrity... loading package files... checking for file conflicts... :: Processing package changes... installing cython... installing python-packaging... installing python-pyproject-hooks... installing python-build... Optional dependencies for python-build python-pip: to use as the Python package installer (default) python-uv: to use as the Python package installer python-virtualenv: to use virtualenv for build isolation installing python-installer... installing python-more-itertools... installing python-jaraco.functools... installing python-jaraco.context... installing python-autocommand... installing python-jaraco.text... Optional dependencies for python-jaraco.text python-inflect: for show-newlines script installing python-jaraco.collections... installing python-platformdirs... installing python-wheel... Optional dependencies for python-wheel python-keyring: for wheel.signatures python-xdg: for wheel.signatures python-setuptools: for legacy bdist_wheel subcommand [pending] installing python-setuptools... installing python-setuptools-scm... installing python-pycparser... installing python-cffi... Optional dependencies for python-cffi python-setuptools: "limited api" version checking in cffi.setuptools_ext [installed] installing python-cryptography... installing python-oscrypto... installing python-iniconfig... installing python-pluggy... installing python-pytest... installing botan... Optional dependencies for botan boost-libs: for the botan executable python: for using botan2.py [installed] installing softhsm... :: Running post-transaction hooks... (1/1) Arming ConditionNeedsUpdate... [?25h==> Retrieving sources...  -> Found python-pkcs11-0.7.0.tar.gz  -> Found python-pkcs11_mark-tests-as-xfail.patch  -> Found use-functools-cached-property.patch ==> WARNING: Skipping all source file integrity checks. ==> Extracting sources...  -> Extracting python-pkcs11-0.7.0.tar.gz with bsdtar ==> Starting prepare()... patching file pkcs11/types.py patching file requirements.txt patching file tests/test_ecc.py patching file tests/test_x509.py ==> Starting build()... * Getting build dependencies for wheel... * Building wheel... /usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml does not contain a tool.setuptools_scm section' Traceback (most recent call last): File "/usr/lib/python3.13/site-packages/setuptools_scm/_integration/pyproject_reading.py", line 36, in read_pyproject section = defn.get("tool", {})[tool_name] ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^ KeyError: 'setuptools_scm' running bdist_wheel running build running build_py creating build/lib.linux-riscv64-cpython-313/pkcs11 copying pkcs11/defaults.py -> build/lib.linux-riscv64-cpython-313/pkcs11 copying pkcs11/mechanisms.py -> build/lib.linux-riscv64-cpython-313/pkcs11 copying pkcs11/constants.py -> build/lib.linux-riscv64-cpython-313/pkcs11 copying pkcs11/exceptions.py -> build/lib.linux-riscv64-cpython-313/pkcs11 copying pkcs11/__init__.py -> build/lib.linux-riscv64-cpython-313/pkcs11 copying pkcs11/types.py -> build/lib.linux-riscv64-cpython-313/pkcs11 creating build/lib.linux-riscv64-cpython-313/pkcs11/util copying pkcs11/util/rsa.py -> build/lib.linux-riscv64-cpython-313/pkcs11/util copying pkcs11/util/dh.py -> build/lib.linux-riscv64-cpython-313/pkcs11/util copying pkcs11/util/x509.py -> build/lib.linux-riscv64-cpython-313/pkcs11/util copying pkcs11/util/dsa.py -> build/lib.linux-riscv64-cpython-313/pkcs11/util copying pkcs11/util/__init__.py -> build/lib.linux-riscv64-cpython-313/pkcs11/util copying pkcs11/util/ec.py -> build/lib.linux-riscv64-cpython-313/pkcs11/util running egg_info writing python_pkcs11.egg-info/PKG-INFO writing dependency_links to python_pkcs11.egg-info/dependency_links.txt writing requirements to python_pkcs11.egg-info/requires.txt writing top-level names to python_pkcs11.egg-info/top_level.txt reading manifest file 'python_pkcs11.egg-info/SOURCES.txt' adding license file 'LICENSE' writing manifest file 'python_pkcs11.egg-info/SOURCES.txt' copying pkcs11/_errors.pyx -> build/lib.linux-riscv64-cpython-313/pkcs11 copying pkcs11/_mswin.pxd -> build/lib.linux-riscv64-cpython-313/pkcs11 copying pkcs11/_pkcs11.pyx -> build/lib.linux-riscv64-cpython-313/pkcs11 copying pkcs11/_pkcs11_defn.pxd -> build/lib.linux-riscv64-cpython-313/pkcs11 copying pkcs11/_utils.pyx -> build/lib.linux-riscv64-cpython-313/pkcs11 running build_ext warning: pkcs11/_pkcs11.pyx:17:0: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310 warning: pkcs11/_errors.pyx:85:44: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. warning: pkcs11/_pkcs11.pyx:1366:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310 warning: pkcs11/_pkcs11.pyx:1390:8: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310 warning: pkcs11/_pkcs11.pyx:1421:8: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310 performance hint: pkcs11/_errors.pyx:85:6: Exception check on 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:196:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:211:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:219:70: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:219:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:230:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:268:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:274:28: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:282:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:303:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:316:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:336:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:363:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:366:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:380:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:427:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:488:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:566:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:582:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:590:63: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:590:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:606:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:609:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:616:51: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:615:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:633:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:640:32: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:646:32: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:651:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:656:64: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:656:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:720:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:731:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:747:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:759:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:769:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:855:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:892:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:896:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:903:56: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:902:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:935:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:947:74: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:946:28: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:957:67: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:957:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:983:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:987:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:994:55: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:993:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1026:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:1038:74: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:1037:28: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:1048:67: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:1048:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1074:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1077:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:1084:52: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:1083:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1105:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1115:28: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1120:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:1125:65: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:1125:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1150:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1152:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1172:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1182:28: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1186:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1210:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:1217:59: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:1216:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1276:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1338:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1409:38: Exception check after calling 'C_GetFunctionList' will always require the GIL to be acquired. Declare 'C_GetFunctionList' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. performance hint: pkcs11/_pkcs11.pyx:1409:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1432:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1439:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1470:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. warning: pkcs11/_pkcs11.pyx:1478:64: Use boundscheck(False) for faster access performance hint: pkcs11/_pkcs11.pyx:1478:20: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1487:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1556:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1557:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. performance hint: pkcs11/_pkcs11.pyx:1562:24: Exception check after calling 'assertRV' will always require the GIL to be acquired. Possible solutions: 1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2. Use an 'int' return type on 'assertRV' to allow an error code to be returned. Compiling pkcs11/_pkcs11.pyx because it changed. [1/1] Cythonizing pkcs11/_pkcs11.pyx building 'pkcs11._pkcs11' extension creating build/temp.linux-riscv64-cpython-313/pkcs11 gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -march=rv64gc -mabi=lp64d -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fno-omit-frame-pointer -g -ffile-prefix-map=/build/python/src=/usr/src/debug/python -flto=auto -ffat-lto-objects -march=rv64gc -mabi=lp64d -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fno-omit-frame-pointer -g -ffile-prefix-map=/build/python/src=/usr/src/debug/python -flto=auto -march=rv64gc -mabi=lp64d -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fno-omit-frame-pointer -g -ffile-prefix-map=/build/python/src=/usr/src/debug/python -flto=auto -march=rv64gc -mabi=lp64d -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fno-omit-frame-pointer -g -ffile-prefix-map=/build/python-python-pkcs11/src=/usr/src/debug/python-python-pkcs11 -flto=auto -fPIC -I/usr/include/python3.13 -c pkcs11/_pkcs11.c -o build/temp.linux-riscv64-cpython-313/pkcs11/_pkcs11.o ^[[A^[[C^[[B^[[B                gcc -shared -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -flto=auto -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -flto=auto -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -flto=auto -march=rv64gc -mabi=lp64d -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fno-omit-frame-pointer -g -ffile-prefix-map=/build/python-python-pkcs11/src=/usr/src/debug/python-python-pkcs11 -flto=auto build/temp.linux-riscv64-cpython-313/pkcs11/_pkcs11.o -L/usr/lib -o build/lib.linux-riscv64-cpython-313/pkcs11/_pkcs11.cpython-313-riscv64-linux-gnu.so installing to build/bdist.linux-riscv64/wheel running install running install_lib creating build/bdist.linux-riscv64/wheel creating build/bdist.linux-riscv64/wheel/pkcs11 copying build/lib.linux-riscv64-cpython-313/pkcs11/defaults.py -> build/bdist.linux-riscv64/wheel/./pkcs11 copying build/lib.linux-riscv64-cpython-313/pkcs11/mechanisms.py -> build/bdist.linux-riscv64/wheel/./pkcs11 copying build/lib.linux-riscv64-cpython-313/pkcs11/constants.py -> build/bdist.linux-riscv64/wheel/./pkcs11 copying build/lib.linux-riscv64-cpython-313/pkcs11/exceptions.py -> build/bdist.linux-riscv64/wheel/./pkcs11 copying build/lib.linux-riscv64-cpython-313/pkcs11/__init__.py -> build/bdist.linux-riscv64/wheel/./pkcs11 copying build/lib.linux-riscv64-cpython-313/pkcs11/types.py -> build/bdist.linux-riscv64/wheel/./pkcs11 creating build/bdist.linux-riscv64/wheel/pkcs11/util copying build/lib.linux-riscv64-cpython-313/pkcs11/util/rsa.py -> build/bdist.linux-riscv64/wheel/./pkcs11/util copying build/lib.linux-riscv64-cpython-313/pkcs11/util/dh.py -> build/bdist.linux-riscv64/wheel/./pkcs11/util copying build/lib.linux-riscv64-cpython-313/pkcs11/util/x509.py -> build/bdist.linux-riscv64/wheel/./pkcs11/util copying build/lib.linux-riscv64-cpython-313/pkcs11/util/dsa.py -> build/bdist.linux-riscv64/wheel/./pkcs11/util copying build/lib.linux-riscv64-cpython-313/pkcs11/util/__init__.py -> build/bdist.linux-riscv64/wheel/./pkcs11/util copying build/lib.linux-riscv64-cpython-313/pkcs11/util/ec.py -> build/bdist.linux-riscv64/wheel/./pkcs11/util copying build/lib.linux-riscv64-cpython-313/pkcs11/_errors.pyx -> build/bdist.linux-riscv64/wheel/./pkcs11 copying build/lib.linux-riscv64-cpython-313/pkcs11/_mswin.pxd -> build/bdist.linux-riscv64/wheel/./pkcs11 copying build/lib.linux-riscv64-cpython-313/pkcs11/_pkcs11.pyx -> build/bdist.linux-riscv64/wheel/./pkcs11 copying build/lib.linux-riscv64-cpython-313/pkcs11/_pkcs11_defn.pxd -> build/bdist.linux-riscv64/wheel/./pkcs11 copying build/lib.linux-riscv64-cpython-313/pkcs11/_utils.pyx -> build/bdist.linux-riscv64/wheel/./pkcs11 copying build/lib.linux-riscv64-cpython-313/pkcs11/_pkcs11.cpython-313-riscv64-linux-gnu.so -> build/bdist.linux-riscv64/wheel/./pkcs11 running install_egg_info Copying python_pkcs11.egg-info to build/bdist.linux-riscv64/wheel/./python_pkcs11-0.7.0-py3.13.egg-info running install_scripts creating build/bdist.linux-riscv64/wheel/python_pkcs11-0.7.0.dist-info/WHEEL creating '/build/python-python-pkcs11/src/python-pkcs11-0.7.0/dist/.tmp-swfd8987/python_pkcs11-0.7.0-cp313-cp313-linux_riscv64.whl' and adding 'build/bdist.linux-riscv64/wheel' to it adding 'pkcs11/__init__.py' adding 'pkcs11/_errors.pyx' adding 'pkcs11/_mswin.pxd' adding 'pkcs11/_pkcs11.cpython-313-riscv64-linux-gnu.so' adding 'pkcs11/_pkcs11.pyx' adding 'pkcs11/_pkcs11_defn.pxd' adding 'pkcs11/_utils.pyx' adding 'pkcs11/constants.py' adding 'pkcs11/defaults.py' adding 'pkcs11/exceptions.py' adding 'pkcs11/mechanisms.py' adding 'pkcs11/types.py' adding 'pkcs11/util/__init__.py' adding 'pkcs11/util/dh.py' adding 'pkcs11/util/dsa.py' adding 'pkcs11/util/ec.py' adding 'pkcs11/util/rsa.py' adding 'pkcs11/util/x509.py' adding 'python_pkcs11-0.7.0.dist-info/LICENSE' adding 'python_pkcs11-0.7.0.dist-info/METADATA' adding 'python_pkcs11-0.7.0.dist-info/WHEEL' adding 'python_pkcs11-0.7.0.dist-info/top_level.txt' adding 'python_pkcs11-0.7.0.dist-info/RECORD' removing build/bdist.linux-riscv64/wheel Successfully built python_pkcs11-0.7.0-cp313-cp313-linux_riscv64.whl ==> Starting check()... Slot 0 has a free/uninitialized token. The token has been initialized and is reassigned to slot 980570584 ============================= test session starts ============================== platform linux -- Python 3.13.1, pytest-8.3.4, pluggy-1.5.0 rootdir: /build/python-python-pkcs11/src/python-pkcs11-0.7.0 collected 70 items tests/test_aes.py ....ss. [ 10%] tests/test_des.py .... [ 15%] tests/test_dh.py ... [ 20%] tests/test_digest.py .... [ 25%] tests/test_dsa.py ... [ 30%] tests/test_ecc.py .s...x [ 38%] tests/test_iterators.py x. [ 41%] tests/test_public_key_external.py .s.. [ 47%] tests/test_rsa.py ....... [ 57%] tests/test_sessions.py .............. [ 77%] tests/test_slots_and_tokens.py ........ [ 88%] tests/test_threading.py Fatal Python error: Segmentation fault Thread 0x000070a194ffa160 (most recent call first): File "/build/python-python-pkcs11/src/python-pkcs11-0.7.0/tests/test_threading.py", line 27 in thread_work File "/usr/lib/python3.13/threading.py", line 992 in run File "/usr/lib/python3.13/threading.py", line 1041 in _bootstrap_inner File "/usr/lib/python3.13/threading.py", line 1012 in _bootstrap Current thread 0x000070a195bfc160 (most recent call first): File "/build/python-python-pkcs11/src/python-pkcs11-0.7.0/tests/test_threading.py", line 28 in thread_work File "/usr/lib/python3.13/threading.py", line 992 in run File "/usr/lib/python3.13/threading.py", line 1041 in _bootstrap_inner File "/usr/lib/python3.13/threading.py", line 1012 in _bootstrap Thread 0x000070a1967fe160 (most recent call first): File "/build/python-python-pkcs11/src/python-pkcs11-0.7.0/tests/test_threading.py", line 28 in thread_work File "/usr/lib/python3.13/threading.py", line 992 in run File "/usr/lib/python3.13/threading.py", line 1041 in _bootstrap_inner File "/usr/lib/python3.13/threading.py", line 1012 in _bootstrap Thread 0x000070a196fff160 (most recent call first): File "/build/python-python-pkcs11/src/python-pkcs11-0.7.0/tests/test_threading.py", line 28 in thread_work File "/usr/lib/python3.13/threading.py", line 992 in run File "/usr/lib/python3.13/threading.py", line 1041 in _bootstrap_inner File "/usr/lib/python3.13/threading.py", line 1012 in _bootstrap Thread 0x000070a1a8839020 (most recent call first): File "/usr/lib/python3.13/threading.py", line 359 in wait File "/usr/lib/python3.13/threading.py", line 659 in wait File "/usr/lib/python3.13/threading.py", line 979 in start File "/build/python-python-pkcs11/src/python-pkcs11-0.7.0/tests/test_threading.py", line 41 in test_concurrency File "/build/python-python-pkcs11/src/python-pkcs11-0.7.0/tests/__init__.py", line 95 in wrapper File "/usr/lib/python3.13/unittest/case.py", line 606 in _callTestMethod File "/usr/lib/python3.13/unittest/case.py", line 651 in run File "/usr/lib/python3.13/unittest/case.py", line 707 in __call__ File "/usr/lib/python3.13/site-packages/_pytest/unittest.py", line 351 in runtest File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 174 in pytest_runtest_call File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 103 in _multicall File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 513 in __call__ File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 242 in File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 341 in from_call File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 241 in call_and_report File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 132 in runtestprotocol File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 113 in pytest_runtest_protocol File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 103 in _multicall File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 513 in __call__ File "/usr/lib/python3.13/site-packages/_pytest/main.py", line 362 in pytest_runtestloop File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 103 in _multicall File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 513 in __call__ File "/usr/lib/python3.13/site-packages/_pytest/main.py", line 337 in _main File "/usr/lib/python3.13/site-packages/_pytest/main.py", line 283 in wrap_session File "/usr/lib/python3.13/site-packages/_pytest/main.py", line 330 in pytest_cmdline_main File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 103 in _multicall File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 513 in __call__ File "/usr/lib/python3.13/site-packages/_pytest/config/__init__.py", line 175 in main File "/usr/lib/python3.13/site-packages/_pytest/config/__init__.py", line 201 in console_main File "/usr/bin/pytest", line 8 in Extension modules: pkcs11._pkcs11, _cffi_backend (total: 2) /startdir/PKGBUILD: line 39: 2992 Segmentation fault PYTHONPATH="$PWD/build/lib.linux-$CARCH-cpython-$_python_version" pytest --import-mode=append ==> ERROR: A failure occurred in check().  Aborting... ==> ERROR: Build failed, check /var/lib/archbuild/extra-riscv64/root26/build [?25h[?25hreceiving incremental file list python-python-pkcs11-0.7.0-9-riscv64-build.log python-python-pkcs11-0.7.0-9-riscv64-check.log python-python-pkcs11-0.7.0-9-riscv64-prepare.log sent 81 bytes received 3,965 bytes 2,697.33 bytes/sec total size is 41,937 speedup is 10.37