Source: golang-github-spf13-viper
Version: 1.6.1-1
Severity: normal
X-Debbugs-Cc: [email protected]

Hi,

I'm going to update golang-github-mitchellh-mapstructure to latest release 
1.3.2.
It includes my PR https://github.com/mitchellh/mapstructure/pull/155
And will cause viper FTBFS,

=== RUN   TestBindPFlagsIntSlice
    TestBindPFlagsIntSlice: viper_test.go:927:
                Error Trace:    viper_test.go:927
                Error:          Not equal:
                                expected: []int(nil)
                                actual  : []int{}

                                Diff:
                                --- Expected
                                +++ Actual
                                @@ -1,2 +1,3 @@
                                -([]int) <nil>
                                +([]int) {
                                +}

                Test:           TestBindPFlagsIntSlice

I have asked on upstream last year,
https://github.com/spf13/viper/issues/579

I think the test before viper 1.3.0 is correct.
The current test is bug with a bug mapstructure version.

However to ease the testing migration of golang-github-mitchellh-mapstructure,
I think I need to disable this test for a while.

Any objection?

Thanks
Shengjing Zhu

Reply via email to