Closed
Conversation
after 2038 something in test1915 fails on 32-bit OSes
bagder
approved these changes
Jul 30, 2021
Member
bagder
left a comment
There was a problem hiding this comment.
Extending life of these tests by seven years. OK!
Member
|
Thanks! |
Contributor
Author
|
Still would be good to find out why test1915 fails with a 2038 date on 32-bit OSes - I think other tests passed. |
Member
|
I think you mean 32 bit This might explain it: Lines 488 to 491 in 8d0c113 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
after 2038 something in (or behind) test1915 fails on 32-bit OSes.
It will need fixing within the next years.