Your message dated Tue, 5 Jun 2018 22:38:20 +0200
with message-id <[email protected]>
and subject line Re: [pkg-go] Bug#841575: docker-registry: FTBFS: Tests failures
has caused the Debian Bug report #841575,
regarding docker-registry: FTBFS: Test failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
841575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841575
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: docker-registry
Version: 2.4.1~ds1-2
Severity: serious
Tags: stretch sid
User: [email protected]
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> PASS
> ok github.com/docker/distribution/registry/storage/driver/swift 38.958s
> ? github.com/docker/distribution/registry/storage/driver/testsuites
> [no test files]
> ? github.com/docker/distribution/testutil [no test files]
> === RUN TestUUID4Generation
> --- PASS: TestUUID4Generation (0.00s)
> === RUN TestParseAndEquality
> --- PASS: TestParseAndEquality (0.01s)
> PASS
> ok github.com/docker/distribution/uuid 0.011s
> ?
> github.com/docker/distribution/vendor/github.com/Azure/azure-sdk-for-go/storage
> [no test files]
> ? github.com/docker/distribution/vendor/github.com/docker/goamz/aws
> [no test files]
> ? github.com/docker/distribution/vendor/github.com/docker/goamz/s3
> [no test files]
> ? github.com/docker/distribution/version [no test files]
> dh_auto_test: go test -v -p 1 -test.short github.com/docker/distribution
> github.com/docker/distribution/cmd/digest
> github.com/docker/distribution/cmd/registry
> github.com/docker/distribution/cmd/registry-api-descriptor-template
> github.com/docker/distribution/configuration
> github.com/docker/distribution/context
> github.com/docker/distribution/contrib/token-server
> github.com/docker/distribution/digest github.com/docker/distribution/health
> github.com/docker/distribution/health/api
> github.com/docker/distribution/manifest
> github.com/docker/distribution/manifest/manifestlist
> github.com/docker/distribution/manifest/schema1
> github.com/docker/distribution/manifest/schema2
> github.com/docker/distribution/notifications
> github.com/docker/distribution/reference
> github.com/docker/distribution/registry
> github.com/docker/distribution/registry/api/errcode
> github.com/docker/distribution/registry/api/v2
> github.com/docker/distribution/registry/auth
> github.com/docker/distribution/registry/auth/htpasswd
> github.com/docker/distribution/registry/auth/silly
> github.com/docker/distribution/registry/auth/token
> github.com/docker/distribution/registry/client
> github.com/docker/distribution/registry/client/auth
> github.com/docker/distribution/registry/client/transport
> github.com/docker/distribution/registry/listener
> github.com/docker/distribution/registry/middleware/registry
> github.com/docker/distribution/registry/middleware/repository
> github.com/docker/distribution/registry/proxy
> github.com/docker/distribution/registry/proxy/scheduler
> github.com/docker/distribution/registry/storage
> github.com/docker/distribution/registry/storage/cache
> github.com/docker/distribution/registry/storage/cache/cachecheck
> github.com/docker/distribution/registry/storage/cache/memory
> github.com/docker/distribution/registry/storage/cache/redis
> github.com/docker/distribution/registry/storage/driver
> github.com/docker/distribution/registry/storage/driver/azure
> github.com/docker/distribution/registry/storage/driver/base
> github.com/docker/distribution/registry/storage/driver/factory
> github.com/docker/distribution/registry/storage/driver/filesystem
> github.com/docker/distribution/registry/storage/driver/gcs
> github.com/docker/distribution/registry/storage/driver/inmemory
> github.com/docker/distribution/registry/storage/driver/middleware
> github.com/docker/distribution/registry/storage/driver/middleware/cloudfront
> github.com/docker/distribution/registry/storage/driver/oss
> github.com/docker/distribution/registry/storage/driver/s3-aws
> github.com/docker/distribution/registry/storage/driver/s3-goamz
> github.com/docker/distribution/registry/storage/driver/swift
> github.com/docker/distribution/registry/storage/driver/testsuites
> github.com/docker/distribution/testutil github.com/docker/distribution/uuid
> github.com/docker/distribution/vendor/github.com/Azure/azure-sdk-for-go/storage
> github.com/docker/distribution/vendor/github.com/docker/goamz/aws
> github.com/docker/distribution/vendor/github.com/docker/goamz/s3
> github.com/docker/distribution/version returned exit code 1
> debian/rules:11: recipe for target 'override_dh_auto_test' failed
If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185
If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.
The full build log is available from:
http://aws-logs.debian.net/2016/10/21/docker-registry_2.4.1~ds1-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 2.6.2~ds1-2
On Sun, Nov 20, 2016 at 08:37:29PM -0800, Tianon Gravi wrote:
> On 20 November 2016 at 20:31, Tianon Gravi <[email protected]> wrote:
> > I wasn't able to dig into the details yet, but looking at the log I
> > noticed the following which I believe is the real test failure output:
>
> That being said, I currently get the (more severe IMO) failure when
> trying to build locally:
>
> > src/github.com/docker/distribution/registry/registry.go:13:2: cannot find
> > package "github.com/Sirupsen/logrus/formatters/logstash" in any of:
> > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/docker/distribution/vendor/github.com/Sirupsen/logrus/formatters/logstash
> > (vendor tree)
> > /usr/lib/go-1.7/src/github.com/Sirupsen/logrus/formatters/logstash (from
> > $GOROOT)
> > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/Sirupsen/logrus/formatters/logstash
> > (from $GOPATH)
I'm not able to reproduce any build failure currently and the logrus
problem seems to have been explicitly fixed in the latest upload by
onlyjob (which also built fine on official buildds).
He seems to have forgot to close this report, so I'm doing that now.
Regards,
Andreas Henriksson
--- End Message ---
