Fix test glitch in PersistenceProvider_Memory_FixedLatency_WriteRead #6378
Conversation
This file contains 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
Failure mode:
```
Write: Expected minimum latency = 00:00:00.2000000 Actual = 00:00:00.1975619
at Tester.AzureUtils.Persistence.PersistenceProviderTests_Local.PersistenceProvider_Memory_FixedLatency_WriteRead()
in C:\agent\_work\2\s\test\Extensions\TesterAzureUtils\Persistence\PersistenceProviderTests.cs:line 237
```
This looks to be caused by a simple system clock resolution / rounding error edge case glitch in the test code.
jthelin
deleted the
Test-glitch-PersistenceProvider_Memory_FixedLatency_WriteRead
branch
sergeybykov
pushed a commit
to sergeybykov/orleans
that referenced
this pull request
Apr 24, 2020
…otnet#6378) (cherry picked from commit 1228928)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Failure mode:
This looks to be caused by a simple system clock resolution / rounding error edge case glitch in the test code.
This is a fix for a test glitch encountered with running Functional tests for PR #6374