-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Build failures due to Timestamp precision #8782
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
Comments
eleftherias
added a commit
that referenced
this issue
Jul 1, 2020
eleftherias
added a commit
that referenced
this issue
Jul 1, 2020
It appears this is still an issue on Windows. |
I wonder if when the issue is fixed with Windows, this commit can also be reverted: a0a9718 |
akohli96
pushed a commit
to akohli96/spring-security
that referenced
this issue
Aug 25, 2021
This is possible because of the update to HSQLDB 2.6.0 This reverts commit eb7b276. Closes spring-projectsgh-8782
akohli96
pushed a commit
to akohli96/spring-security
that referenced
this issue
Aug 25, 2021
This reverts commit 09a0670. This appears to still be an issue in Windows Issue spring-projectsgh-8782
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tests relying on HSQLDB 2.5.1 are failing because of https://sourceforge.net/p/hsqldb/bugs/1585/
We will temporarily change our assertions on Timestamp values to be more lenient (to the millisecond).
The text was updated successfully, but these errors were encountered: