#1007744 dovecot: FTBFS on ppc64el

Package:
src:dovecot
Source:
dovecot
Submitter:
Sebastian Ramacher
Date:
2022-07-02 18:33:03 UTC
Severity:
serious
Tags:
#1007744#5
Date:
2022-03-15 22:22:23 UTC
From:
To:
Source: dovecot
Version: 1:2.3.18+dfsg1-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)

dovecot FTBFS on ppc64el:

0 / 77 tests failed
slow server .......................................................... : ok
slow client .......................................................... : ok
hanging command payload .............................................. : ok
bad command .......................................................... : ok
many bad commands .................................................... : ok
long command ......................................................... : ok
SERVER: Fatal: Server timed out
make[4]: *** [Makefile:1346: check-local] Error 1

See
https://buildd.debian.org/status/fetch.php?pkg=dovecot&arch=ppc64el&ver=1%3A2.3.18%2Bdfsg1-1%2Bb1&stamp=1647334386&raw=0

Cheers
#1007744#10
Date:
2022-04-13 19:33:58 UTC
From:
To:
It looks like the ppc64el build was retried and succeeded.

Maybe the timeouts should be increased for slow build systems, similar
what upstream did for running under valgrind with commit 2d12409a
("lib-smtp: Adjust test timeouts based on valgrind runtime
presence")[1].


[1]: https://github.com/dovecot/core/commit/2d12409a41ea0824c76693502fbfe93d72013c8e
#1007744#13
Date:
2022-04-13 19:33:58 UTC
From:
To:
It looks like the ppc64el build was retried and succeeded.

Maybe the timeouts should be increased for slow build systems, similar
what upstream did for running under valgrind with commit 2d12409a
("lib-smtp: Adjust test timeouts based on valgrind runtime
presence")[1].


[1]: https://github.com/dovecot/core/commit/2d12409a41ea0824c76693502fbfe93d72013c8e
#1007744#18
Date:
2022-04-17 02:43:02 UTC
From:
To:
Build logs are available at (1) and don't look like a timeout.  It was
rebuilt on a different machine (2), though, which could be relevant.  I
wonder if there's a different configuration.  Every dovecot build on
mipsel-manda-04 has failed since 2021-09-04, across a few different
versions.  We have seen one failure on mipsel-osuosl-04 that was
successful on retry, though, so it could be a red herring.

I haven't had a chance to look into this more deeply.

1.  https://buildd.debian.org/status/fetch.php?pkg=dovecot&arch=mips64el&ver=1%3A2.3.18%2Bdfsg1-1%2Bb1&stamp=1647208211&raw=0
2. https://buildd.debian.org/status/logs.php?pkg=dovecot&arch=mips64el
#1007744#23
Date:
2022-04-25 09:15:40 UTC
From:
To:
The test-program-client-net is listen()ing on 127.0.0.1 in test_program_setup(). Then in test_program_refused() it tries to connect to ::1 -> 127.0.0.3 -> 127.0.0.2 -> 127.0.0.1 and expects that only the last one succeeds and the others fail with "connection refused". But for some reason more than the last of those connects are succeeding. So bind()ing to the listener socket somehow isn't working as expected.
#1007744#28
Date:
2022-04-25 21:27:47 UTC
From:
To:
I bet this build host doesn't have an IPv4 configuration.  This has come
up previously as an issue:
https://lists.debian.org/debian-devel/2020/07/msg00070.html

We have successfully built on the host mipsel-manda-04 before, but it
was with an older version of dovecot (2.3.4.1)

noah
#1007744#33
Date:
2022-05-16 20:46:16 UTC
From:
To:
All ppc64el buildds are pretty fast, timeout problems due to slow
buildds are usually on other architectures.

cu
Adrian
#1007744#38
Date:
2022-07-02 18:31:34 UTC
From:
To:
The last few builds all built fine. Let's assume this issue was fixed.

Cheers