Flaky test: DockerTrustSuite.SetUpTest (more apparent on ARM?) #19393
Description
02:46:42
02:46:42 ----------------------------------------------------------------------
02:46:42 FAIL: check_test.go:130: DockerTrustSuite.SetUpTest
02:46:42
02:46:42 check_test.go:132:
02:46:42 s.not = setupNotary(c)
02:46:42 github.com/docker/docker/integration-cli/_test/_obj_test/trust_server.go:136:
02:46:42 ...open github.com/docker/docker/integration-cli/_test/_obj_test/trust_server.go: no such file or directory
02:46:42 ... Error: Timeout waiting for test notary to become available: Get https://localhost:4443/v2/: dial tcp [::1]:4443: getsockopt: connection refused
02:46:42
02:46:42
02:46:42 ----------------------------------------------------------------------
02:46:42 PANIC: docker_cli_build_test.go:5831: DockerTrustSuite.TestBuildContextDirIsSymlink
02:46:42
02:46:42 ... Panic: Fixture has panicked (see related PANIC)
02:46:42
02:46:42 ----------------------------------------------------------------------
Also, as reported by @StefanScherer #19379 (comment)
I have seen the error in DockerTrustSuite.SetUpTest in our ARM builds. Reproduceable there, but hadn't the time for a closer look.
I guess this loop in integration-cli/trust_server.go waiting 10 .. 50 ms is very optimistic for the notary-server to become available for the tests.