Arvados

----------------------------------------------------------------------
FAIL: integration_test.go:42: IntegrationSuite.SetUpSuite
…
[z3333] time="2025-04-17T19:07:33.488693876Z" level=info msg="supervisor shut down" PID=24964 error="context canceled" 
[z1111] time="2025-04-17T19:07:33.490200619Z" level=info msg="supervisor shut down" PID=24964 error="context canceled" 
integration_test.go:151:
    c.Assert(ok, check.Equals, true)
... obtained bool = false
... expected bool = true

OOPS: 63 passed, 1 FAILED, 25 MISSED
--- FAIL: Test (35.06s)
FAIL
coverage: 82.0% of statements
FAIL    git.arvados.org/arvados.git/lib/controller    35.078s
FAIL
======= lib/controller tests -- FAILED
======= test lib/controller -- 37s

I am guessing this is the "main" error:

[z2222] [controller] time="2025-04-17T19:07:24.725019233Z" level=error msg=exiting error="listen tcp 127.0.0.22:34949: bind: address already in use" 
[z2222] time="2025-04-17T19:07:24.726899226Z" level=error msg="task failed" PID=24964 error="[/tmp/arvados-server-boot-1530107467/bin/arvados-server controller -config /tmp/arvados-server-boot-1530107467/config.yml]: error: exit status 1" task=controller
[z2222] time="2025-04-17T19:07:24.726955403Z" level=info msg="shutting down" PID=24964

Did we really just get unlucky with port selection? And if so, it would be better if this was the error that got reported by SetUpSuite, rather than a generic timeout.

Full log attached.

Full log attached.