FTBFS: zfp has test failures on Lunar (most architectures)

Bug #2000012 reported by Hans Joachim Desserud
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
h5z-zfp (Ubuntu)
Fix Released
Undecided
Unassigned
numcodecs (Ubuntu)
Fix Released
Undecided
Unassigned
zfp (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

zfp 1.0.0-5 currently fails to build on Ubuntu Lunar on most architectures.

For some reason the package has built successfully on Debian Sid, and I have not been able to reproduce the issue there myself either. So whatever is causing it seems to be Ubuntu specific.

The error message is:
[100%] Linking C shared module ../bin/zfpy.cpython-310-x86_64-linux-gnu.so
cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/python && /usr/bin/cmake -E cmake_link_script CMakeFiles/zfpy.dir/link.txt --verbose=1
/usr/bin/cc -fPIC -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,--unresolved-symbols=ignore-all -Wl,--version-script="/<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/python/CMakeFiles/zfpy-version-script.map" -Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto -Wl,-z,relro -Wl,-z,now -shared -o ../bin/zfpy.cpython-310-x86_64-linux-gnu.so CMakeFiles/zfpy.dir/zfpy.c.o -Wl,-rpath,/<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/lib/x86_64-linux-gnu: ../lib/x86_64-linux-gnu/libzfp.so.1.0.0
make[3]: Leaving directory '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build'
[100%] Built target testzfp
make[3]: Leaving directory '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build'
[100%] Built target zfpy
make[2]: Leaving directory '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build'
make[1]: *** [Makefile:149: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build'
dh_auto_build: error: cd .pybuild/cpython3_3.10/build && make -j4 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2
E: pybuild pybuild:379: build: plugin cmake failed with: exit code=25: dh_auto_build --buildsystem=cmake --builddirectory=/<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build --
dh_auto_build: error: pybuild --build -i python{version} -p "3.11 3.10" returned exit code 13
make: *** [debian/rules:20: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

(taken from the amd64 build log https://bugs.launchpad.net/ubuntu/+source/zfp/1.0.0-5/+build/24892707/+files/buildlog_ubuntu-lunar-amd64.zfp_1.0.0-5_BUILDING.txt.gz )

At first I thought the linking failed, but upon further inspection it looks like the actual problem occur right after the linking has finished...

Tags: ftbfs lunar
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

This in turn cause dependency wait failures for numcodecs and h5z-zfp which are waiting for python3-zfpy and libzfp-dev, respectively.

Revision history for this message
Graham Inggs (ginggs) wrote :

zfp (1.0.0-5ubuntu1) lunar; urgency=medium

  * Cherry-pick upstream commit to avoid FTBFS with LTO

 -- Graham Inggs <email address hidden> Mon, 30 Jan 2023 07:02:49 +0000

Changed in zfp (Ubuntu):
status: New → Fix Committed
Revision history for this message
Graham Inggs (ginggs) wrote :

Weird that these missing builds did not appear on update_excuses, but maybe that's because this package only ever built on armhf and riscv64.

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for the fix.

> Weird that these missing builds did not appear on update_excuses

Yes, I originally found them on https://launchpad.net/ubuntu/lunar/+builds?build_text=&build_state=depwait&arch_tag=amd64 and tried to tie together the ones with common root cause. I suspect that since the build was also missing in previous versions update_excuses concludes that its at least not worse than it was and checks the successfully built arches for regressions.

Changed in numcodecs (Ubuntu):
status: New → Fix Committed
Changed in h5z-zfp (Ubuntu):
status: New → Fix Released
Changed in zfp (Ubuntu):
status: Fix Committed → Fix Released
Changed in numcodecs (Ubuntu):
status: Fix Committed → 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.