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
Run dist_move_chunk as a solo test in PG15 #5248
Run dist_move_chunk as a solo test in PG15 #5248
Conversation
d5698f4
to
38d68bf
Compare
Codecov Report
@@ Coverage Diff @@
## main #5248 +/- ##
=======================================
Coverage 89.01% 89.01%
=======================================
Files 225 225
Lines 51807 51807
=======================================
Hits 46117 46117
Misses 5690 5690
Continue to review full report at Codecov.
|
38d68bf
to
a000b2d
Compare
@svenklemm, @sb230132: please review this pull request.
|
When run in a parallel group, the dist_move_chunk test can get into a deadlock with another test running a 'DROP DATABASE' command. So, mark it as a solo test to disallow it from running in a parallel group. Closes timescale#4972
a000b2d
to
3892744
Compare
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.
LGTM 👍
Automated backport to 2.9.x not done: cherry-pick failed. |
When run in a parallel group, the dist_move_chunk test can get into a deadlock with another test running a 'DROP DATABASE' command. So, mark it as a solo test to disallow it from running in a parallel group.
Closes #4972
Disable-check: force-changelog-changed