Hi, On Mon, Apr 05, 2021 at 10:14:47PM +0200, Paul Gevers wrote: > Control: severity -1 serious > Control: retitle -1 debci: autopkgtest regularly times out > > Hi Chris, > > On 02-04-2021 22:13, Chris Hofstaedtler wrote: > > This can also be seen on armhf, and amd64: > > > > https://ci.debian.net/data/autopkgtest/testing/armhf/d/debci/11403517/log.gz > > https://ci.debian.net/data/autopkgtest/testing/amd64/d/debci/11311391/log.gz > > > > Might make sense to disable this test for bullseye if it cannot be fixed? > > I think you're right, we should disable the test-suite test until we > figure out what's wrong. > > What I see in all the logs I checked is something like: > Error: operation wait on node debci-test@ci-091-b3ce2841 timed out. > Timeout value used: 10000 > > For amd64, it mostly happens (but not always) on our worker13, which is > our multi debci runner amd64 host. So it seems that our test-suite is > not reliable on hosts which have multiple debci runners.
This reminded me of #956152. I looked into the debci test suite and realized the functional tests always start the test rabbitmq-server with a fixed node name prefix, and that's probably why this happens. I will use the hostname and and a random value for the node name - that should do the trick.
signature.asc
Description: PGP signature