-
Notifications
You must be signed in to change notification settings - Fork 901
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
[Flaky test] cagg_insert interleaves output differently #5331
Labels
flaky-test
Issue about a flaky test
Comments
Merged
mkindahl
added a commit
to mkindahl/timescaledb
that referenced
this issue
Sep 28, 2023
Isolation test `cagg_insert` is flaky because refresh steps can complete in any order. Adding constraints so that completion is reported in the same order in all test runs. Fixes timescale#5331
mkindahl
added a commit
to mkindahl/timescaledb
that referenced
this issue
Sep 28, 2023
Isolation test `cagg_insert` is flaky because refresh steps can complete in any order. Adding constraints so that completion is reported in the same order in all test runs. Fixes timescale#5331
mkindahl
added a commit
that referenced
this issue
Sep 28, 2023
Isolation test `cagg_insert` is flaky because refresh steps can complete in any order. Adding constraints so that completion is reported in the same order in all test runs. Fixes #5331
konskov
pushed a commit
to konskov/timescaledb
that referenced
this issue
Oct 6, 2023
Isolation test `cagg_insert` is flaky because refresh steps can complete in any order. Adding constraints so that completion is reported in the same order in all test runs. Fixes timescale#5331 (cherry picked from commit 6bef59a)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which test is flaky?
cagg_insert
Since when has the test been flaky?
February 14, 2023
Link to the failed test run
https://github.com/timescale/timescaledb/actions/runs/4175600633/jobs/7233369995
Log output
Reason for flakiness
No response
The text was updated successfully, but these errors were encountered: