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

roachtest: Added a declarative schema changer job compatibility tests #98403

Merged

Conversation

Xiang-Gu
Copy link
Contributor

@Xiang-Gu Xiang-Gu commented Mar 10, 2023

We added a roachtest to test declarative schema change job compatibility, both
forward and backward, in a mixed version state (V22_2/V23_1).

Fixes: #89345
Epic: None
Release Note: None

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@Xiang-Gu Xiang-Gu changed the title roachtest: Add mixed version state job compaticility test v222, v231 WIP: roachtest: Add mixed version state job compaticility test v222, v231 Mar 10, 2023
@Xiang-Gu Xiang-Gu force-pushed the revive-222-231-mixed-version-roachtest branch 3 times, most recently from 0c8ee05 to 11ea354 Compare March 13, 2023 15:41
@Xiang-Gu Xiang-Gu changed the title WIP: roachtest: Add mixed version state job compaticility test v222, v231 WIP: roachtest: Added a declarative schema changer job compatibility tests Mar 13, 2023
@Xiang-Gu Xiang-Gu force-pushed the revive-222-231-mixed-version-roachtest branch from 11ea354 to f766dd3 Compare March 13, 2023 15:46
@Xiang-Gu Xiang-Gu requested a review from a team March 13, 2023 15:47
@Xiang-Gu Xiang-Gu marked this pull request as ready for review March 13, 2023 16:52
@Xiang-Gu Xiang-Gu requested a review from a team as a code owner March 13, 2023 16:53
@Xiang-Gu Xiang-Gu requested review from herkolategan and srosenberg and removed request for a team March 13, 2023 16:53
@Xiang-Gu Xiang-Gu changed the title WIP: roachtest: Added a declarative schema changer job compatibility tests roachtest: Added a declarative schema changer job compatibility tests Mar 13, 2023
fqazi
fqazi previously requested changes Mar 13, 2023
Copy link
Collaborator

@fqazi fqazi left a comment

Choose a reason for hiding this comment

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

:lgtm:

This gives good coverage of at least basic sanity between the two releases.

Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @herkolategan, @srosenberg, and @Xiang-Gu)


-- commits line 4 at r1:
spelling: revived

typo: ensured => ensures

Code quote:

revivied

pkg/cmd/roachtest/tests/mixed_version_job_compatibility_in_declarative_schema_changer.go line 89 at r1 (raw file):

) versionStep {
	return func(ctx context.Context, t test.Test, u *versionUpgradeTest) {
		planAndRunSchemaChange(ctx, t, c, nodeIDs.RandNode(), `DROP SEQUENCE testdb.testsc.s`)

There is overlap here, we can probably have functions that call each other. Also, I'm wondering if master should only test against the previous release, and we backport the roachtest to 22.2

This PR revived a previously skipped roachtest that tests declarative
schema changer job compatibility in the mixed version state (V22_2/V23_1).
@Xiang-Gu Xiang-Gu force-pushed the revive-222-231-mixed-version-roachtest branch from f766dd3 to b36c525 Compare March 13, 2023 21:41
@chengxiong-ruan
Copy link
Contributor

chengxiong-ruan commented Mar 13, 2023

Could you also update the PR description. I was looking for another test for V22_1/V22_2 heh (the commit message is correct :)). Thanks.

Copy link
Contributor Author

@Xiang-Gu Xiang-Gu left a comment

Choose a reason for hiding this comment

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

Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (and 1 stale) (waiting on @fqazi, @herkolategan, and @srosenberg)


-- commits line 4 at r1:

Previously, fqazi (Faizan Qazi) wrote…

spelling: revived

typo: ensured => ensures

Done.


pkg/cmd/roachtest/tests/mixed_version_job_compatibility_in_declarative_schema_changer.go line 89 at r1 (raw file):

Previously, fqazi (Faizan Qazi) wrote…

There is overlap here, we can probably have functions that call each other. Also, I'm wondering if master should only test against the previous release, and we backport the roachtest to 22.2

I don't want to separate the overlap here because those stmts have "dependency" (e.g. we should alter a table before dropping it). However, I do like your idea of having only one roachtest on master and backporting the other one to 22.2 (#98541).

@Xiang-Gu
Copy link
Contributor Author

@chengxiong-ruan Sorry, I separate that roachtest into a backport PR to 22.2.

@Xiang-Gu
Copy link
Contributor Author

TFTR!

bors r+

@craig
Copy link
Contributor

craig bot commented Mar 13, 2023

👎 Rejected by code reviews

Copy link
Contributor

@ajwerner ajwerner left a comment

Choose a reason for hiding this comment

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

LGTM

@ajwerner ajwerner requested a review from fqazi March 13, 2023 22:34
@ajwerner
Copy link
Contributor

bors r+

@craig
Copy link
Contributor

craig bot commented Mar 13, 2023

👎 Rejected by code reviews

@ajwerner ajwerner dismissed fqazi’s stale review March 13, 2023 22:34

There were only nits

@ajwerner
Copy link
Contributor

bors r+

@craig
Copy link
Contributor

craig bot commented Mar 13, 2023

This PR was included in a batch that was canceled, it will be automatically retried

@craig
Copy link
Contributor

craig bot commented Mar 14, 2023

Build succeeded:

@craig craig bot merged commit 25c00d4 into cockroachdb:master Mar 14, 2023
@Xiang-Gu Xiang-Gu deleted the revive-222-231-mixed-version-roachtest branch March 14, 2023 14:51
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.

tests: Revive a skipped roachtest when master is 23.1
5 participants