Fix last change precision - #1669
Merged
Merged
Conversation
The strptime format rejected fractional seconds and non-positive offsets. Signed-off-by: Mattias Walström <lazzer@gmail.com>
Truncating the realtime and monotonic clocks separately before subtracting let the same stamp read one second apart on consecutive GETs. Compute the offset from full-precision timespecs and floor it once. Signed-off-by: Mattias Walström <lazzer@gmail.com>
troglobit
approved these changes
Sep 28, 2026
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
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.
This actually fix a flaky test on x86, when testing for last-changed the changes sometimes got in the same second, therfore failed.
Description
Checklist
Tick relevant boxes, this PR is-a or has-a: