-
Notifications
You must be signed in to change notification settings - Fork 37
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
Updating RethinkDb to 1.12 breaks tests #171
Comments
Thanks for bringing this up, Dale. Looks like there are 16 test failures. Two classes of failures, one is some of the reduce tests, and the other is all of the grouping tests. I suppose the real question in fixing these is whether there's any value to maintaining compatibility with the pre-1.12 RethinkDB releases; that'd make this a potentially complicated fix. I'd probably lean towards not having backward compatibility. I'll probably find some time to look into these errors this weekend, or within a week at the latest, but if anyone else is interested in taking a look, feel free! Reduce tests are failing like this:
Group tests are failing like this:
|
I have some time this evening, I plan to fix this unless you have already started. |
I haven't gotten anything started on this. Thanks Karl. |
Looks like need to regenerate rethinkdb_spec.proto, when I diff what we have with the rethinkdb repo it appears all the terms that are failing our tests are included in the new one. I'll get that generated and checked in after work today. |
Nm...was able to regenerate on the train, running the tests now. |
Bad assumption, that introduced other failures. I think I'm on the right track, though. |
If you're going to regenerate the protobuf stuff, note that there is a script to do so in the the rethinkdb-net directory. Some post processing is done as part of the script to fix some compile issues. |
Yessir, I used that. Afterwards (it cleanly created everything) I re-ran the tests and there were similar failures, so I think that was wrong of me to assume that was the source of the issue. I think it's in our code, though I am going to investigate later to eliminate guessing. |
+1 vote for dropping support for pre-1.12. RethinkDB offers a migration path for people interested in the latest and greatest. Otherwise there can always be an older branch of this project. |
Fixed be PR #173. |
Just updated my local machine and the CI server to RethinkDb 1.12.3. I then ran the test suite and we have some failing tests. This version must have some breaking changes. I haven't dug into them yet, just creating an issue for reference.
The text was updated successfully, but these errors were encountered: