-
Notifications
You must be signed in to change notification settings - Fork 31
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
test: re-enable async_no_yield
test from vconnect
test group
#471
test: re-enable async_no_yield
test from vconnect
test group
#471
Conversation
We have deadlock here, either Tarantool's integration tests fails with vshard or testing on master fails in vshard. PR should be merged right before tarantool/tarantool#9803 (review), backporting to 2.11 should be also done immediately. The other option is to delete |
47bd082
to
0ad7fec
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.
If we'll go this way, we'll have failing CI for some time either in vshard on in master. The alternative of removing this test completely until the time, everything is merged is better IMO. @Gerold103, what do you think?
P.S. Failure of test_locate_master
is caused by test_async_no_yield
After the fix for tarantool/tarantool#9489 bug was merged, we can now re-enable the test to reflect the correct behaviour in versions to which the fix was backported to. Closes tarantool#456 NO_DOC=<test>
0ad7fec
to
b28f63b
Compare
async_no_yield
test from vconnect
test groupasync_no_yield
test from vconnect
test group
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.
Thank you for the patch! No objections
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.
Thanks for the patch!
This patch re-enables the test to reflect the correct behavior after the fix for tarantool/tarantool#9489 bug was merged.
Closes #456