Your message dated Sat, 31 Jan 2026 08:15:15 +0200
with message-id <[email protected]>
and subject line Re: Bug#1126605: pytest-codspeed: FTBFS with the nocheck build
profile
has caused the Debian Bug report #1126605,
regarding pytest-codspeed: FTBFS with the nocheck build profile
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1126605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126605
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:pytest-codspeed
Version: 4.2.0-1
Severity: serious
Tags: forky sid ftbfs
User: [email protected]
Usertags: ftbfs-nocheck-profile
Dear maintainer:
During a rebuild of all packages in unstable using the nocheck build profile,
this package failed to build.
Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:
https://people.debian.org/~sanvila/build-logs/202601/
A wiki page discussing how to reproduce bugs in this category and
possible solutions is available here:
https://wiki.debian.org/qa.debian.org/FTBFS/nocheck
(It's a wiki, so you are welcome to contribute)
About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.
If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:pytest-codspeed, so that this is still
visible in the BTS web page for this package.
Thanks.
--------------------------------------------------------------------------------
[...]
debian/rules clean
dh clean --buildsystem=pybuild
debian/rules override_dh_auto_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_clean
rm -rf .mypy_cache .pytest_cache
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_autoreconf_clean -O--buildsystem=pybuild
dh_clean -O--buildsystem=pybuild
debian/rules binary
dh binary --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:142: Building wheel for python3.14 with "build"
module
I: pybuild base:384: python3.14 -m build --skip-dependency-check --no-isolation
--wheel --outdir /<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_pytest_codspeed
* Building wheel...
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py",
line 389, in <module>
main()
~~~~^^
File
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py",
line 373, in main
json_out["return_val"] = hook(**hook_input["kwargs"])
~~~~^^^^^^^^^^^^^^^^^^^^^^^^
File
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py",
line 280, in build_wheel
return _build_backend().build_wheel(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
wheel_directory, config_settings, metadata_directory
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 435, in
build_wheel
return _build(['bdist_wheel'])
File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 426, in
_build
return self._build_with_temp_dir(
~~~~~~~~~~~~~~~~~~~~~~~~~^
cmd,
^^^^
...<3 lines>...
self._arbitrary_args(config_settings),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 407, in
_build_with_temp_dir
self.run_setup()
~~~~~~~~~~~~~~^^
File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 320, in
run_setup
exec(code, locals())
~~~~^^^^^^^^^^^^^^^^
File "<string>", line 14, in <module>
File "<frozen importlib._bootstrap_external>", line 759, in exec_module
File "<frozen importlib._bootstrap>", line 491, in _call_with_frames_removed
File "/<<PKGBUILDDIR>>/src/pytest_codspeed/instruments/hooks/build.py", line
3, in <module>
from cffi import FFI # type: ignore
^^^^^^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'cffi'
ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:483: build: plugin pyproject failed with: exit code=1:
python3.14 -m build --skip-dependency-check --no-isolation --wheel --outdir
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_pytest_codspeed
I: pybuild plugin_pyproject:142: Building wheel for python3.13 with "build"
module
I: pybuild base:384: python3.13 -m build --skip-dependency-check --no-isolation
--wheel --outdir /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_pytest_codspeed
* Building wheel...
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py",
line 389, in <module>
main()
~~~~^^
File
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py",
line 373, in main
json_out["return_val"] = hook(**hook_input["kwargs"])
~~~~^^^^^^^^^^^^^^^^^^^^^^^^
File
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py",
line 280, in build_wheel
return _build_backend().build_wheel(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
wheel_directory, config_settings, metadata_directory
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 435, in
build_wheel
return _build(['bdist_wheel'])
File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 426, in
_build
return self._build_with_temp_dir(
~~~~~~~~~~~~~~~~~~~~~~~~~^
cmd,
^^^^
...<3 lines>...
self._arbitrary_args(config_settings),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 407, in
_build_with_temp_dir
self.run_setup()
~~~~~~~~~~~~~~^^
File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 320, in
run_setup
exec(code, locals())
~~~~^^^^^^^^^^^^^^^^
File "<string>", line 14, in <module>
File "<frozen importlib._bootstrap_external>", line 1023, in exec_module
File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
File "/<<PKGBUILDDIR>>/src/pytest_codspeed/instruments/hooks/build.py", line
3, in <module>
from cffi import FFI # type: ignore
^^^^^^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'cffi'
ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:483: build: plugin pyproject failed with: exit code=1:
python3.13 -m build --skip-dependency-check --no-isolation --wheel --outdir
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_pytest_codspeed
dh_auto_build: error: pybuild --build -i python{version} -p "3.14 3.13"
returned exit code 13
make: *** [debian/rules:19: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit
status 2
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Version: 3.2.0-2
Hello,
Am 30.01.26 um 17:40 schrieb Santiago Vila:
On Fri, Jan 30, 2026 at 02:36:26PM +0000, Colin Watson wrote:
On Thu, Jan 29, 2026 at 01:57:37PM +0000, Santiago Vila wrote:
[...]
File "/<<PKGBUILDDIR>>/src/pytest_codspeed/instruments/hooks/build.py", line 3, in
<module>
from cffi import FFI # type: ignore
^^^^^^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'cffi'
Now that I look at it, I already fixed this bug in version 3.2.0-2,
when I reported it as #1116846.
I forgot completely about such bug, probably because it was already
archived, and reported it again as #1126605 now.
The problem with 4.2.0-1 in the archive is that it seems to have been
made as if 3.2.0-2 never existed. That would explain how the bug was
"unfixed", but the fact that 3.2.0-2 exists in the git repo looks
like a mystery for me.
then it's probably my fault and I screwed things while working on
preparing 4.2.0 in the git tree. But I can't really remember as it's
almost some months ago this did happen.
I think it's a useless spending of time trying to figure out what did
happen here, the issue the report is about was corrected in 3.2.0-2 so
no real work to do atm. That's why I use this email to also close the
report.
--
Regards
Carsten
--- End Message ---
