-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Unit tests flaking in CI #1559
Comments
Another one: https://github.com/open-telemetry/opentelemetry-go/pull/1551/checks?check_run_id=1936404855 (Go 1.15 only)
|
It's worth noting that CI runs each test multiple times (386 vs x64, with/without coverage), and there's no pattern to which of these fail in a given run. |
Fixes open-telemetry#1559. Some unit tests were flaking in CI because they expected the timestamp to advance during a test, when it's possible for it to be unchanged instead. This change switches the offending "<" comparisons to "<=".
* Vendor Thrift dependency * Fix build * Changelog entry * Ignore third_party for coverage purposes * Re-run tests * Re-run tests * Re-run tests * Re-run tests * Relax time comparisons Fixes #1559. Some unit tests were flaking in CI because they expected the timestamp to advance during a test, when it's possible for it to be unchanged instead. This change switches the offending "<" comparisons to "<=". * Re-run tests * Relax more time comparisons * Re-run tests Co-authored-by: Tyler Yahn <[email protected]>
I'm consistently seeing this failure for testing ubuntu-latest for Go 1.14 and 1.15 on both 386 and amd64 architecture. E.g. https://github.com/open-telemetry/opentelemetry-go/runs/1956584735?check_suite_focus=true |
I'm testing this locally with:
but have yet to reproduce the failure. |
I am able to reliably reproduce the error locally while not running the race detector. When I add the |
@Aneurysm9 that is interesting for sure! What system are you running on and what command do you run to reproduce? |
* Stagger timestamps in exact aggregator tests Fixes #1559. * Missed one * Yield while you wait * Just sleep for a teeny tiny bit * Oops, wrong PR in Changelog * Make sure that *some* time passes * Keep time comparisons relaxed
* Vendor Thrift dependency * Fix build * Changelog entry * Ignore third_party for coverage purposes * Re-run tests * Re-run tests * Re-run tests * Re-run tests * Relax time comparisons Fixes open-telemetry#1559. Some unit tests were flaking in CI because they expected the timestamp to advance during a test, when it's possible for it to be unchanged instead. This change switches the offending "<" comparisons to "<=". * Re-run tests * Relax more time comparisons * Re-run tests Co-authored-by: Tyler Yahn <[email protected]>
* Stagger timestamps in exact aggregator tests Fixes open-telemetry#1559. * Missed one * Yield while you wait * Just sleep for a teeny tiny bit * Oops, wrong PR in Changelog * Make sure that *some* time passes * Keep time comparisons relaxed
While working on #1551, I ran into several unit tests that flaked in CI:
https://github.com/open-telemetry/opentelemetry-go/runs/1930834290
(Go 1.14 only)
https://github.com/open-telemetry/opentelemetry-go/runs/1931724468
(Go 1.15 only)
https://github.com/open-telemetry/opentelemetry-go/runs/1931857269
(Go 1.14 only)
I wasn't able to reproduce any of these locally, even when I ran the tests 10000 times.
The text was updated successfully, but these errors were encountered: