Hi! This package appears to sometimes fail during build, seen on
riscv64 like this:
5068s === RUN TestProxyManifestGetByTag
5068s time="2026-06-12T11:06:19Z" level=warning msg="No HTTP secret provided - generated random secret. This may cause problems with uploads if multiple registries are behind a load-balancer. To provide a shared secret, fill in http.secret in the configuration file or set the REGISTRY_HTTP_SECRET environment variable." go.version=go1.26.4
5068s time="2026-06-12T11:06:19Z" level=info msg="redis not configured" go.version=go1.26.4
5068s time="2026-06-12T11:06:21Z" level=info msg="response completed" go.version=go1.26.4 http.request.host="127.0.0.1:36599" http.request.id=62cdb771-ed54-4a10-b55b-1d007f85a787 http.request.method=POST http.request.remoteaddr="127.0.0.1:40486" http.request.uri=/v2/foo/bar/blobs/uploads/ http.request.useragent=Go-http-client/1.1 http.response.duration=10.299038ms http.response.status=202 http.response.written=0
5068s 127.0.0.1 - - [12/Jun/2026:11:06:21 +0000] "POST /v2/foo/bar/blobs/uploads/ HTTP/1.1" 202 0 "" "Go-http-client/1.1"
5068s panic: test timed out after 1h0m0s
5068s running tests:
5068s TestProxyManifestGetByTag (1m42s)
https://ci.debian.net/packages/d/docker-registry/testing/riscv64/71982609/#L3711
It has passed debci sometimes, see
https://ci.debian.net/packages/d/docker-registry/testing/riscv64/
https://ci.debian.net/packages/d/docker-registry/testing/riscv64/71984080/
so I assume this is triggered by a slow machine, and could be fixed by
extending the timeout further with this patch to debian/rules:
- dh_auto_test -- -test.short -test.timeout=1h
+ dh_auto_test -- -test.short -test.timeout=2h
/Simon