-
Notifications
You must be signed in to change notification settings - Fork 13
Fix DateTime test #513
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
Fix DateTime test #513
Conversation
Test started failing because 4.4 servers with the UTC patch started appearing. The test did not account for all implications of the new protocol specs.
return map(lambda x: getattr(x, "value", x), rec.values) | ||
|
||
self._create_driver_and_session() | ||
server_supports_utc = get_server_info().has_utc_patch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is it not a simple boolean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, I found out why below.
maybe it could be renamed server_version_may_support_utc
:P
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, for 4.4 and 4.3 there's no straight-forward way for TestKit to know if the server supports the UTC patch or not. So this value can be 1
yes, 0
no, and 0.5
maybe 😬
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
trilean.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might we consider an enum?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📅
Test started failing because 4.4 servers with the UTC patch started appearing.
The test did not account for all implications of the new protocol specs.