Your message dated Mon, 19 May 2025 08:38:35 +0000
with message-id <e1ugw15-0033sd...@fasolo.debian.org>
and subject line Bug#1103105: fixed in cthreadpool 0.0+git20231218.4eb5a69-2
has caused the Debian Bug report #1103105,
regarding cthreadpool: FTBFS in testing/i386: E: Build killed with signal TERM 
after 150 minutes of inactivity
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 ow...@bugs.debian.org
immediately.)


-- 
1103105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cthreadpool
Version: 0.0+git20231218.4eb5a69-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20250414 ftbfs-trixie

Hi,

During a rebuild of all packages in testing (trixie), your package failed
to build on i386.


Relevant part (hopefully):
>    dh_update_autotools_config
>    dh_autoreconf
>    debian/rules override_dh_auto_test
> make[1]: Entering directory 
> '/build/reproducible-path/cthreadpool-0.0+git20231218.4eb5a69'
> cd tests ; \
> for i in normal_compile.sh optimized_compile.sh ; \
> do \
>       echo; \
>       echo Testing $i; \
>       ./$i; \
> done
> 
> Testing normal_compile.sh
> Adding up to 100 with 4 threads
> Adding up to 100 with 1000 threads
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2025/04/14/cthreadpool_0.0+git20231218.4eb5a69-1_testing-i386.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250414;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250414&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message ---
Source: cthreadpool
Source-Version: 0.0+git20231218.4eb5a69-2
Done: Andreas Tille <ti...@debian.org>

We believe that the bug you reported is fixed in the latest version of
cthreadpool, 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 1103...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille <ti...@debian.org> (supplier of updated cthreadpool 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 ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Mon, 19 May 2025 08:31:39 +0200
Source: cthreadpool
Architecture: source
Version: 0.0+git20231218.4eb5a69-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Andreas Tille <ti...@debian.org>
Closes: 1103105
Changes:
 cthreadpool (0.0+git20231218.4eb5a69-2) unstable; urgency=medium
 .
   * Team upload.
   * Build (== run test suite) only on 64 bit architectures since
     it seems 32 bit architectures are causing long processing
     Closes: #1103105
   * Mark build time test depends as such
Checksums-Sha1:
 62a0d74571dd8e94420f13ba605431a7faadba96 2209 
cthreadpool_0.0+git20231218.4eb5a69-2.dsc
 c0badb1a95983a317f4abeabfcf93a8d10d2c09f 3876 
cthreadpool_0.0+git20231218.4eb5a69-2.debian.tar.xz
 ec350b745b6810114160022416a8fe87930b3ce4 6546 
cthreadpool_0.0+git20231218.4eb5a69-2_amd64.buildinfo
Checksums-Sha256:
 981bc05c468b094a4589b1e00eb92d5ebb98a96236559cd09e10c9bca246270f 2209 
cthreadpool_0.0+git20231218.4eb5a69-2.dsc
 8a9e0f3be4a8215101949aa1c4e1787f0994d5340b3f29555a02a48c8f9f0bc6 3876 
cthreadpool_0.0+git20231218.4eb5a69-2.debian.tar.xz
 fbf13c4807e174fe6f2b5ff95a1023970de919d6ac0daba84033bdd08417d88d 6546 
cthreadpool_0.0+git20231218.4eb5a69-2_amd64.buildinfo
Files:
 8e1ab443250716e627d1f4363cb34d24 2209 libs optional 
cthreadpool_0.0+git20231218.4eb5a69-2.dsc
 458f4e452bbb041a1f413dbf8a7f63a5 3876 libs optional 
cthreadpool_0.0+git20231218.4eb5a69-2.debian.tar.xz
 7afc4ada7be9940375f3992657cce6de 6546 libs optional 
cthreadpool_0.0+git20231218.4eb5a69-2_amd64.buildinfo

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

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmgq42oRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtF5cQ//TFEVAWEnmGRwTj2kmLs9DMoU5B6WbQsm
JEiGsNnF73MfguVzVgfyJBJcHx18ng9ANZIm5WNLVR6puvECAZTu0Vg3kEL6EudV
4kCLCTf8TCM9nWGLaGQ524t48unxPOQ+1CJQthQEt9pPsYFuSno7u0X1SQpKWXju
crdt1m1ZjVSNKBvuHWsx98IU2gDXC0E9DyMmoefdtPm0Z+UnlHVgDRViPT3tX0e1
Klw8I2LKTZPC2mVoqflXwJf+apzrovNvk278KgPgtreGj3wuYwWPYYbajxDh9AUl
gtmkM/DYU43AbqJ3hLpW0mbhs7rf+VtO72mACWwaNFZQ/OqLSvRT8Kosy0aiR9aE
2prJKQDhAeW0L5x1tvIrjIKsko6MPftD+ZvA004zpD8YxyaL8zRmYvFVHInoQ0Dp
Ph1ftNDpBhmscDrdOcQQfqFgvDLA/FIRGDEfgIn7GInS2ln0Yuh0YSfhZ8hTLWTG
IoOkdOamq2ihQbteH7DywXh1eHvJOIYRaAFcNTD/lxcTQtW+aUw4Bhw2yv0Tm0/t
KzI1KZqYEijVZrpmmGSIO8FE+EG4UadaFNgPmeryZWxw009Gm/9dx++DXJl6L+vV
VBNAMfwwksFZ4HaXJ01Hz+oganKYLE13SeUywQ+yjjzWyTHTiPMIVtRazQSVr6kD
/yDzjLTni8k=
=fuTK
-----END PGP SIGNATURE-----

Attachment: pgp5EMzdz75wn.pgp
Description: PGP signature


--- End Message ---

Reply via email to