Fix random integration test failure due to timestamp roll over #224
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.
Description:
After #218 there is a second test that randomly fails due to a roll over in a timestamp:
Resetting the timestamp as in aforementioned PR should solve that issue.
The second changed test is more a preventive measure. Using
assertManyRequestSetsAreEqual
(and the nestedassertRequestsAreEqual
) should take care of minute differences in timestamps.Review