Your message dated Mon, 15 Dec 2025 09:22:59 +0000
with message-id <[email protected]>
and subject line Bug#1122627: fixed in cadical 2.1.3-2
has caused the Debian Bug report #1122627,
regarding cadical: FTBFS on riscv64 due to test timeout
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.)


-- 
1122627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122627
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: cadical
Version: 2.1.3-1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: [email protected]
User: [email protected]
Usertags: riscv64

Dear maintainer,

cadical fails to build from source on riscv64 with a timeout in one test:

| test/api/run.sh: using CXX=g++
| test/api/run.sh: using CXXFLAGS=-g -O2 
-ffile-prefix-map=/build/reproducible-path/cadical-2.1.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -DNBUILD -fPIC -Wall 
-Wextra -O3 -DNDEBUG
| test/api/run.sh: using CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2
| test/api/run.sh: using LDFLAGS=-Wl,-z,relro -Wl,-z,now
| test/api/run.sh: running API test 'parcompwrite'
| g++ -g -O2 -ffile-prefix-map=/build/reproducible-path/cadical-2.1.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -DNBUILD -fPIC -Wall 
-Wextra -O3 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -o 
../build/test-api-parcompwrite.o -c ../test/api/parcompwrite.cpp
| g++ -g -O2 -ffile-prefix-map=/build/reproducible-path/cadical-2.1.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -DNBUILD -fPIC -Wall 
-Wextra -O3 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -o 
../build/test-api-parcompwrite ../build/test-api-parcompwrite.o -Wl,-z,relro 
-Wl,-z,now -L../build -lcadical
| ../build/test-api-parcompwrite
| error: unexpected alarm (file I/O hanging?)
| # 0 ... failed (non-zero exit code)

...

| test/api/run.sh: API testing results: 15 ok, 1 failed
| make[3]: *** [makefile:3: api] Error 1
| make[3]: Leaving directory '/build/reproducible-path/cadical-2.1.3/test'
| make[2]: *** [makefile:103: test] Error 2
| make[2]: Leaving directory '/build/reproducible-path/cadical-2.1.3/build'
| make[1]: *** [makefile:17: test] Error 2
| make[1]: Leaving directory '/build/reproducible-path/cadical-2.1.3'
| dh_auto_test: error: make -j4 test TESTSUITEFLAGS="-j4 --verbose" VERBOSE=1 
returned exit code 2
| make: *** [debian/rules:12: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

The full build log is available here:
https://buildd.debian.org/status/fetch.php?pkg=cadical&arch=riscv64&ver=2.1.3-1&stamp=1765299510&raw=0

It appears that the new test-api-parcompwrite test contains a timeout,
which is too low for riscv64 (and hppa). The following patch fixes that
by increasing it from 1 to 2 seconds:

--- cadical-2.1.3.orig/test/api/parcompwrite.cpp
+++ cadical-2.1.3/test/api/parcompwrite.cpp
@@ -248,7 +248,7 @@ static void catch_alarm (int sig) {
 int main () {
   const char *suffixes[] = {"", ".gz"};
   (void) ::signal (SIGALRM, catch_alarm);
-  ::alarm (1);
+  ::alarm (2);
   for (auto s : suffixes) {
     suffix = s;
     for (unsigned c = 0; c != 2; c++) {

Regards
Aurelien

--- End Message ---
--- Begin Message ---
Source: cadical
Source-Version: 2.1.3-2
Done: Scott Talbert <[email protected]>

We believe that the bug you reported is fixed in the latest version of
cadical, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Scott Talbert <[email protected]> (supplier of updated cadical package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 14 Dec 2025 20:04:17 -0500
Source: cadical
Architecture: source
Version: 2.1.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<[email protected]>
Changed-By: Scott Talbert <[email protected]>
Closes: 1122627
Changes:
 cadical (2.1.3-2) unstable; urgency=medium
 .
   * Extend test timeout to fix FTBFS on riscv64 (Closes: #1122627)
   * Update Standards-Version to 4.7.2 (no changes needed)
Checksums-Sha1:
 ea3e78b78da3000df0ebc8f12c4889ca19f1d57b 1996 cadical_2.1.3-2.dsc
 de87ee2943b7a071cfa4488f0a003223dc0e3f82 4620 cadical_2.1.3-2.debian.tar.xz
 3fc3b9a58087d9c876e9973d1ffeb472e73720f4 6293 cadical_2.1.3-2_amd64.buildinfo
Checksums-Sha256:
 9c7decd99b47992bf716c8cabce7052fcf6ab1f4de9d3b35e6c0d2b852cb8953 1996 
cadical_2.1.3-2.dsc
 35f5be306d270a5cc65cd6f8b2702d72c7c6cb3715412a63cc304ba07a5fbf3c 4620 
cadical_2.1.3-2.debian.tar.xz
 f3b57bf778f78811b86f09d3bd496d1d887a5fdb79cac0c8232a8d54b67a6e64 6293 
cadical_2.1.3-2_amd64.buildinfo
Files:
 8544471715efe6e0db3f8b8d5acb4e53 1996 math optional cadical_2.1.3-2.dsc
 a6ad8ac455029156bb48b5a8e1c07c56 4620 math optional 
cadical_2.1.3-2.debian.tar.xz
 66580180640f9f1eeee9854c54bef389 6293 math optional 
cadical_2.1.3-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmk/YVYPHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3iiBuEQAMEngA/T/rarfM/ofKy+X7fbpiUHkz/miZJb
AaH3jeozwsT6C5kvhLGle8DZfb9M7CQegYEJtyvHpkbfk2JR3d7GpvTB07/usiA5
ZUoajckpr2HWwAuzofhGipKhmKHGkQ1WOZyZQ8Ay+0eyFnDlivAsDNBbXwHEnq2I
TgFKTABzWrMTKd0+wsq+I105ICXfefxCSSyPEhFUIWm5FT3ebFuXVtqQ+ysX8zrD
ixtmGIibt9U9oq0WVZjpnCjI8B1Eq+qhSNMe3KgF+l5hB7DekPzH/91lEUkhhT0a
Bzxauzb397DqoUkTeiPmwfWDC1cpFfcbvzEW0TKcmOO3xgMO0coHng2rKiKvIYEV
Cv4sLU23k5eLAvz0IBGbGZe6JmVSQHGqSRospA5aRTH94m/4U5A3ULV+nufMZ1Qb
OQUxECzP8k2DucrHs1hKi7T+v2ylZo7ppXH3egddVO9D+u2vZkeDNVxnl5+Vob2o
doxSj1FA/GlO74HxR1BJxY+V3haZ0s2vZ9Rc9VgTs7F8kFMAHynjTfaM+H8kHyEH
d4oISpCmpY1cqewldAF1we1gtm/rrp0W2aJT6uaFFLzZJGO2sz953mJ1zbNIRg3N
E2O6JtqGn9Ga5kFHENE/KVL0YFGvUX1YNq3eyMvuMIZyk+6p17boeawNSYfFBbq4
bjwPTeRO
=PfY5
-----END PGP SIGNATURE-----

Attachment: pgpOBJOQUaxgf.pgp
Description: PGP signature


--- End Message ---

Reply via email to