Closed
Conversation
similar to commit f508d29
bagder
approved these changes
Jan 7, 2019
Member
|
Thanks! |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Allow tests to pass by 2037-02-12
similar to commit f508d29
Background:
I found this when working on reproducible builds for openSUSE
where I test if a package build still produces identical results in 15y
and a commit made last November added a 2028 timeout.
Then I raised the bar to +18 years
to get closer to the evil year 2038 and not need such commits for another 3y,
unless regressions are introduced again.
Tested the patch on i586, too.