Your message dated Tue, 16 Jul 2019 20:15:19 +0200
with message-id <[email protected]>
and subject line Re: golang-github-spf13-viper: autopkgtest regression
has caused the Debian Bug report #913975,
regarding golang-github-spf13-viper: autopkgtest regression
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.)
--
913975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913975
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: golang-github-spf13-viper
Version: 1.2.1-1
User: [email protected]
Usertags: regression
Control: affects -1 src:golang-github-mitchellh-mapstructure
[X-Debbugs-CC: [email protected],
[email protected]]
Dear maintainers,
With a recent upload of golang-github-spf13-viper the autopkgtest of
golang-github-spf13-viper fails in testing when that autopkgtest is run
with the binary packages of golang-github-spf13-viper from unstable. It
passes when run with only packages from testing. In tabular form:
pass fail
golang-github-spf13-viper from testing 1.2.1-1
all others from testing from testing
I copied some of the output at the bottom of this report. Looking at the
changelog, and the failure of the new version of
golang-github-mitchellh-mapstructure in testing I see you adapted for
the new version of golang-github-mitchellh-mapstructure but I think you
missed a versioned test dependency on
golang-github-mitchellh-mapstructure. Therefore your test in testing
runs with the old version of golang-github-mitchellh-mapstructure.
Currently this regression is contributing to the delay of the migration
to testing [1]. Can you please investigate the situation and fix it? If
needed, please change the bug's severity.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=golang-github-spf13-viper
https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-spf13-viper/1325733/log.gz
--- FAIL: TestBindPFlagsStringSlice (0.00s)
viper_test.go:613:
Error Trace: viper_test.go:613
Error: Not equal:
expected: []string(nil)
actual : []string{}
Diff:
--- Expected
+++ Actual
@@ -1,2 +1,3 @@
-([]string) <nil>
+([]string) {
+}
Test: TestBindPFlagsStringSlice
viper_test.go:613:
Error Trace: viper_test.go:613
Error: Not equal:
expected: []string(nil)
actual : []string{}
Diff:
--- Expected
+++ Actual
@@ -1,2 +1,3 @@
-([]string) <nil>
+([]string) {
+}
Test: TestBindPFlagsStringSlice
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi,
On Sat, 17 Nov 2018 20:53:18 +0100 Paul Gevers <[email protected]> wrote:
> With a recent upload of golang-github-spf13-viper the autopkgtest of
> golang-github-spf13-viper fails in testing when that autopkgtest is run
> with the binary packages of golang-github-spf13-viper from unstable. It
> passes when run with only packages from testing. In tabular form:
> pass fail
> golang-github-spf13-viper from testing 1.2.1-1
> all others from testing from testing
>
> I copied some of the output at the bottom of this report. Looking at the
> changelog, and the failure of the new version of
> golang-github-mitchellh-mapstructure in testing I see you adapted for
> the new version of golang-github-mitchellh-mapstructure but I think you
> missed a versioned test dependency on
> golang-github-mitchellh-mapstructure. Therefore your test in testing
> runs with the old version of golang-github-mitchellh-mapstructure.
As buster is now released and the test passes everywhere, I don't think
it makes sense to keep this bug open (although theoretical it is still
correct).
Paul
signature.asc
Description: OpenPGP digital signature
--- End Message ---
