-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
118265: rangefeed: improve assertions r=erikgrinaker a=erikgrinaker **rangefeed: use `log.Fatal` instead of panic** This will include the log tags from the context, aiding with debugging. Involves a bunch of context plumbing, and removing some assertion tests. A couple of panics were left in, where it didn't appear natural to plumb through a context. **rangefeed: use pointer receiver in MVCCLogicalOp assertion** `String()` is only implemented for a pointer receiver, so the formatting breaks otherwise. Epic: none Release note: None 118441: mixedversion: add public API to disable individual mutators and rename `finalize` step r=DarrylWong a=renatolabs With this API, tests are now able to disable individual mutators if they are incompatible with the test (e.g., setting a cluster setting that conflicts with what the test is trying to do). Tests should be able to disable mutators with something like the following: ```go mvt := mixedversion.NewTest(..., mixedversion.DisableMutators(mixedversion.ClusterSetting("foo")), ) ``` Note: this is just an example -- individual mutator implementatios are not yet available. **mixedversion: rename `finalizeUpgrade` step to `allowUpgrade`** In the near future, we will randomly change the timing of this step so that it is not immediately followed by migrations, as the name previously suggested. Epic: none Release note: None 118559: opt/exec: try deflaking distsql_tenant_locality again r=yuzefovich a=michae2 In #118168 we tried a retry, but that didn't work. Let's check whether the sql instances are alive. I think this is what `crdb_internal.sql_liveness_is_alive` is for.` Fixes: #117005 Epic: None Release note: None Co-authored-by: Erik Grinaker <[email protected]> Co-authored-by: Renato Costa <[email protected]> Co-authored-by: Michael Erickson <[email protected]>
- Loading branch information
Showing
18 changed files
with
407 additions
and
259 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
47 changes: 47 additions & 0 deletions
47
pkg/cmd/roachtest/roachtestutil/mixedversion/testdata/planner/conflicting_mutators
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
# Tests that we are able to deal with mutators that insert relative to | ||
# steps that are later removed by subsequent mutations. The initial | ||
# insertion should create a concurrent step with user-hooks (see | ||
# `mutator_probabilities` test) and the second mutator removes user | ||
# hooks, flattening that concurrent run. | ||
|
||
add-mutators concurrent_user_hooks_mutator remove_user_hooks_mutator | ||
---- | ||
ok | ||
|
||
# ensure both mutators are always applied | ||
mixed-version-test num_upgrades=1 mutator_probabilities=(concurrent_user_hooks_mutator, 1, remove_user_hooks_mutator, 1) | ||
---- | ||
ok | ||
|
||
in-mixed-version name=(my mixed version feature) | ||
---- | ||
ok | ||
|
||
plan debug=true | ||
---- | ||
mixed-version test plan for upgrading from "v22.2.8" to "<current>" with mutators {concurrent_user_hooks_mutator, remove_user_hooks_mutator}: | ||
├── install fixtures for version "v22.2.8" (1) [stage=cluster-setup] | ||
├── start cluster at version "v22.2.8" (2) [stage=cluster-setup] | ||
├── wait for nodes :1-4 to reach cluster version '22.2' (3) [stage=cluster-setup] | ||
└── upgrade cluster from "v22.2.8" to "<current>" | ||
├── prevent auto-upgrades by setting `preserve_downgrade_option` (4) [stage=init] | ||
├── upgrade nodes :1-4 from "v22.2.8" to "<current>" | ||
│ ├── restart node 4 with binary version <current> (5) [stage=temporary-upgrade] | ||
│ ├── restart node 2 with binary version <current> (6) [stage=temporary-upgrade] | ||
│ ├── restart node 3 with binary version <current> (7) [stage=temporary-upgrade] | ||
│ ├── testSingleStep (8) [stage=temporary-upgrade] | ||
│ └── restart node 1 with binary version <current> (9) [stage=temporary-upgrade] | ||
├── downgrade nodes :1-4 from "<current>" to "v22.2.8" | ||
│ ├── restart node 2 with binary version v22.2.8 (10) [stage=rollback-upgrade] | ||
│ ├── restart node 4 with binary version v22.2.8 (11) [stage=rollback-upgrade] | ||
│ ├── testSingleStep (12) [stage=rollback-upgrade] | ||
│ ├── restart node 1 with binary version v22.2.8 (13) [stage=rollback-upgrade] | ||
│ └── restart node 3 with binary version v22.2.8 (14) [stage=rollback-upgrade] | ||
├── upgrade nodes :1-4 from "v22.2.8" to "<current>" | ||
│ ├── restart node 2 with binary version <current> (15) [stage=last-upgrade] | ||
│ ├── restart node 4 with binary version <current> (16) [stage=last-upgrade] | ||
│ ├── testSingleStep (17) [stage=last-upgrade] | ||
│ ├── restart node 1 with binary version <current> (18) [stage=last-upgrade] | ||
│ └── restart node 3 with binary version <current> (19) [stage=last-upgrade] | ||
├── allow upgrade to happen by resetting `preserve_downgrade_option` (20) [stage=running-upgrade-migrations] | ||
└── wait for nodes :1-4 to reach cluster version <current> (21) [stage=running-upgrade-migrations] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.