-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[internal/otelarrow] Flaky TestMRUReset #34252
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This is failing too much on Windows skipping the test until it is fixed.
**Description:** Ensure the monotonic clock has advanced prior to resetting, to ensure the item generation is before the reset. The monotonic clock is guaranteed to be non-decreasing, but may be identical in consecutive measurements. **Link to tracking Issue:** #34252 **Testing:** I couldn't reproduce the issue locally - this issue would depend on the system clock frequency. **Documentation:** N/A
[EDIT: removed the comment here and moved it to issue #34719] |
[EDIT: removed the comment here and moved it to issue https://github.com//issues/34719] |
@pjanotti are you referring to any/all flaky tests here? I don't see any mention of TestMRUReset in those failures. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
It appears that any timing-based test is unreliable on Windows. |
#### Description Fixes MRU_Reset test. #### Link to tracking issue Fixes #34252 #### Testing This repairs a test by ensuring that a clock advances. #### Documentation n/a
Component(s)
internal/otelarrow
What happened?
Failing here and on main.
Likely introduced in #33579
Collector version
latest
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
No response
Log output
The text was updated successfully, but these errors were encountered: