Skip to content
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: update async_no_yield test from vconnect test group #473

Merged
merged 1 commit into from
Mar 14, 2024

Conversation

CuriousGeorgiy
Copy link
Member

@CuriousGeorgiy CuriousGeorgiy commented Mar 14, 2024

This patch brings an update to the test to reflect the correct behavior after tarantool/tarantool#9489 is fixed. The test against correct behavior is temporarily disabled until tarantol/tarantool#9803 is merged.

This patch needs to be merged before tarantool/tarantool#9803.

Part of #456

After tarantool/tarantool#9489 is fixed, we can update the test to reflect
the correct behaviour. However, we still need to test the incorrect
behaviour for older versions of Tarantool to which the bugfix was not
backported to.

Due to tarantool/tarantool#9489, we have deadlock: either Tarantool's
integration tests fail with vshard or testing against the Tarantool master
version fails in vshard. Let's temporarily disable the assertion that
tests against the correct behaviour in newer Tarantool versions and causes
failure.

Part of tarantool#456

NO_DOC=<test>
Copy link
Contributor

@Serpentian Serpentian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After discussing with @Gerold103 and @sergepetrenko, it was decided to drop the test in order to avoid CI becoming red.

For now, I don't really care, how we'll disable this test for versions >= 2.11, the patch does its job, I'm ok with it.

However, when we'll enable it, it won't be enough to uncomment the line. We'll have to strictly specify versions on which this will or won't work.

E.g. with current check we say, that version 2.11.0-0 (first commit in 2.11.0) will be alright, it won't. We'll have to specify the commit number correctly. The same applies to version 3.0.0 (it will be backported there, won't it?). So, we'll have equality of csw in [2.11.0-n; 3.0.0-0] U [3.0.0-m; infinity]

@Gerold103 Gerold103 self-requested a review March 14, 2024 17:58
Copy link
Collaborator

@Gerold103 Gerold103 left a 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! Just make sure it is re-enabled back when you fix the stuff in core.

@Gerold103 Gerold103 merged commit f4e07ca into tarantool:master Mar 14, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants