-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
consolidating OnlineDDL 'declarative' tests into 'scheduler' tests: part 1 #12061
consolidating OnlineDDL 'declarative' tests into 'scheduler' tests: part 1 #12061
Conversation
…art 1 Signed-off-by: Shlomi Noach <[email protected]>
Review ChecklistHello reviewers! 👋 Please follow this checklist when reviewing this Pull Request. General
If a new flag is being introduced:
If a workflow is added or modified:
Bug fixes
Non-trivial changes
New/Existing features
Backward compatibility
|
Signed-off-by: Shlomi Noach <[email protected]>
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.
I had some minor questions/comments, but nothing blocking. Thank you again! ❤️
t.Run("init: drop table", func(t *testing.T) { | ||
// IF EXISTS is not supported in -declarative | ||
uuid := testOnlineDDL(t, dropIfExistsStatement, "online", "vtgate", "", "") | ||
onlineddl.CheckMigrationStatus(t, &vtParams, shards, uuid, schema.OnlineDDLStatusComplete) |
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.
I'm curious why we have this and the following subtest here since they don't use declarative
? IMO we should remove them as we're not testing the feature and we DO have subtests that confirm they fail.
Same holds true for all of the subtests which aren't using declarativeStrategy
. Perhaps there's good reason to have them here though, which is fine. I do see that you had a comment about this for some towards the end (they're not declarative but fit best in this test).
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.
This particular execution ensures the table does not exist before we begin the actual declarative
testing. In onlineddl_declarative
this was not required, since we started with an empty cluster. But now that we have converged multiple tests into a single workflow, we need to perform pre-test cleanup. Specifically, the particular table actually does exist from a previous test.
I'm not using -declarative
in this DROP TABLE
because I want a "trusted" method before embarking on -declarative
validations.
go/test/endtoend/onlineddl/scheduler/onlineddl_scheduler_test.go
Outdated
Show resolved
Hide resolved
Signed-off-by: Shlomi Noach <[email protected]>
ping for review 🙏 |
Looking for a 2nd review |
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
Followup in #12182 |
…art 1 (#12061) (#1536) * consolidating OnlineDDL 'declarative' tests into 'scheduler' tests: part 1 * increase test timeout * fixed comments --------- Signed-off-by: Shlomi Noach <[email protected]>
Description
Similarly to #12055, the
onlineddl_scheduler
tests now include testing fordeclarative
, effectively makingonlineddl_declarative
redundant.In this PR we do not yet remove
onlineddl_declarative
, because we can't atomically merge the PR while removing arequired
test from the very same PR. A followup PR will remove bothonlineddl_singleton
andonlineddl_declarative
tests and workflows.The objective of this change is to reduce CI workflow files.
Related Issue(s)
#6926
Checklist
Deployment Notes