-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Update a flaky test that fails intermittently in CI #5641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
anmenaga
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leave a comment
| ## The crossgen'ed 'S.M.A.dll' is about 28mb in size, and it would take over 2000ms if we check | ||
| ## each byte of the array, list or collection. We use 200ms as the upper bound value in tests to | ||
| ## prove that we don't check each byte. | ||
| $UpperBoundTime = 200 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previous implementation used some MandatoryFunc to establish a reasonable baseline with adding some extra time to that.
Can $UpperBoundTime use similar runtime-calculated baseline (and adding something on top of that) rather than a constant?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I can add back the baseline and add 200 ms to it
JamesWTruher
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
200ms seems reasonable
|
@anmenaga You comment has been addressed. Can you please take another look? |
|
Thanks all for the review! Since the flaky test could fail in other PR CI runs at any time, I will merge this PR without waiting for 24 hours. |
PR Summary
Close #5627
Update a flaky test that fails intermittently in our CI builds:
The tests were added along with the fix for the issue #5417. The tests are to validate that we don't check each element of a value-type collection argument.
This fix is to increase the upper bound of the expected time to 200ms, which is still way less than the time it would take before the fix -- more than 2000ms for a byte collection of 28mb in size.
PR Checklist
Note: Please mark anything not applicable to this PR
NA.[feature]if the change is significant or affectes feature tests