Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[master]: (spurious?) failures of tests in tsdb/engine/tsm1 when compiled with go master #5854

Closed
jonseymour opened this issue Feb 28, 2016 · 4 comments

Comments

@jonseymour
Copy link
Contributor

The current docker build images used by the influxdata CI appear to compile with go master. Some tests in tsdb/engine/tsm1 fail when compiled with that go version (1d5001af), but not with an earlier version
like 1.6 (7bc40ffb)

A PR which demonstrates that the build failure disappears when using earlier versions of go will be submitted.

The test break is:

=== RUN   Test_IntegerEncoder_Quick
--- FAIL: Test_IntegerEncoder_Quick (0.00s)
    int_test.go:443: mismatch:

        exp=[]

        got=[]

=== RUN   Test_StringEncoder_NoValues
--- PASS: Test_StringEncoder_NoValues (0.00s)
=== RUN   Test_StringEncoder_Single
--- PASS: Test_StringEncoder_Single (0.00s)
=== RUN   Test_StringEncoder_Multi_Compressed
--- PASS: Test_StringEncoder_Multi_Compressed (0.00s)
=== RUN   Test_StringEncoder_Quick
--- FAIL: Test_StringEncoder_Quick (0.00s)
    string_test.go:118: mismatch:

        exp=[]

        got=[]

...

=== RUN   Test_BooleanEncoder_Quick
--- FAIL: Test_BooleanEncoder_Quick (0.00s)
    bool_test.go:100: mismatch:

        exp=[]

        got=[]

@jonseymour
Copy link
Contributor Author

Per ( @marcosnils) discussion in #general on slack.gopher.com, the go change that is responsible for the changed behaviour is possibly:

golang/go@0ccabe2

rather than:

golang/go@a77182f

See: https://gophers.slack.com/archives/general/p1456705357011065

@jonseymour
Copy link
Contributor Author

So, in summary, it seems that the behaviour of testing.quick.Check in go tip has changed in way that is now exercising a code path that is causing a test failure.

The change is that testing.quick.Check() is now generating nil slices for functions with slice arguments when previously it was not.

@jonseymour jonseymour changed the title [master]: spurious failures of tests in tsdb/engine/tsm1 when compiled with go master [master]: (spurious?) failures of tests in tsdb/engine/tsm1 when compiled with go master Feb 29, 2016
@jonseymour
Copy link
Contributor Author

My proposed fix for the issue checks for this case in the Check handler and alters the expected behaviour to the current actual behaviour for this case. If this is not actually the expected behaviour, then a separate issue needs to be raised to fix the expected behaviour.

This fix probably needs to be accepted as is, so that every other build doesn't fail.

jonseymour added a commit to jonseymour/influxdb that referenced this issue Feb 29, 2016
RHS merges cleanly with 0.10.0

Signed-off-by: Jon Seymour <[email protected]>
jonseymour added a commit to jonseymour/influxdb that referenced this issue Feb 29, 2016
jwilder added a commit that referenced this issue Mar 2, 2016
fix tests to cope with future changes to testing.quick.Check - see #5854
@jonseymour
Copy link
Contributor Author

Closed because #5855 has been merged,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant