#1149255 tahoe-lafs: FTBFS against python 3.15rc2

Package:
src:tahoe-lafs
Source:
src:tahoe-lafs
Submitter:
Margarita Manterola
Date:
2026-10-23 13:59:11 UTC
Severity:
normal
Tags:
#1149255#5
Date:
2026-09-28 20:06:05 UTC
From:
To:
Hi!

While rebuilding the python related packages against the Python 3.15rc2
version we found that tahoe-lafs fails to build from source:
https://debusine.debian.net/debian/r-python-python3.15/artifact/4860102/

 From the log, the error seems to be:

allmydata/test/test_crawler.py ..FE.FF
[ 28%]
allmydata/test/test_crypto.py .............................
[ 30%]
allmydata/test/test_deepcheck.py FEFEFEFEFEFE
[ 30%]
allmydata/test/test_deferredutil.py ..............
[ 31%]
allmydata/test/test_dictutil.py .....
[ 31%]
allmydata/test/test_dirnode.py FEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFFEFEFEFE..
[ 32%]
.......FEFEFF
[ 33%]
allmydata/test/test_download.py FFFFFFFFFFFFFFFFFFFFF..FFFFF...FFFFFFFFF
[ 35%]
FF
[ 35%]
allmydata/test/test_eliotutil.py F....F.....F..
[ 36%]
allmydata/test/test_encode.py ....FFFFFFFFFFFFF.FFFF
[ 37%]
allmydata/test/test_encodingutil.py .s...............s...........
[ 39%]
allmydata/test/test_filenode.py .....
[ 39%]
allmydata/test/test_grid_manager.py ...................
[ 40%]
allmydata/test/test_happiness.py ..................
[ 41%]
allmydata/test/test_hashtree.py F...FF...
[ 41%]
allmydata/test/test_hashutil.py ............
[ 42%]
allmydata/test/test_helper.py
E: Build killed with signal TERM after 150 minutes of inactivity

Please note that while we ran into this error during the rebuild against
Python 3.15, that doesn't mean that the root cause for the failure is
necessarily the new Python version.

Setting the severity to important for now. Once Python 3.15 is released,
it will be added to python3-defaults and this bug will become release
critical.

Cheers,
Marga

#1149255#12
Date:
2026-09-29 10:57:53 UTC
From:
To:
Hello,
This is probably a duplicate of #1123360, as tahoe-lafs FTBFS with
Python 3.14 also.

Andrius

#1149255#17
Date:
2026-09-29 13:50:40 UTC
From:
To:
Hi,

Maybe. I filed it as a separate issue because in #1123360 it was about
having test failures, while in this issue it's about reaching 150
minutes of inactivity, i.e. something hangs and never progresses.

I didn't look into why it hangs, so I can't say for sure that it is or
it's not the same root cause.