-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This patch adds two new test configurations, `fakedist-range-tombstone` and `3node-tenant-range-tombstone`, for the SQL logic tests. These write a single, global MVCC range tombstone across the entire user keyspace during cluster bootstrapping. This should not semantically affect the test data written above it, but will activate MVCC range tombstone code paths in the storage layer for testing. Release justification: non-production code changes Release note: None
- Loading branch information
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
load("//build/bazelutil/unused_checker:unused.bzl", "get_x_data") | ||
load("@io_bazel_rules_go//go:def.bzl", "go_test") | ||
|
||
go_test( | ||
name = "fakedist-range-tombstone_test", | ||
size = "enormous", | ||
srcs = ["generated_test.go"], | ||
data = [ | ||
"//c-deps:libgeos", # keep | ||
"//pkg/ccl/logictestccl:testdata", # keep | ||
], | ||
shard_count = 3, | ||
tags = ["cpu:2"], | ||
deps = [ | ||
"//pkg/build/bazel", | ||
"//pkg/ccl", | ||
"//pkg/ccl/utilccl", | ||
"//pkg/security/securityassets", | ||
"//pkg/security/securitytest", | ||
"//pkg/server", | ||
"//pkg/sql/logictest", | ||
"//pkg/testutils/serverutils", | ||
"//pkg/testutils/skip", | ||
"//pkg/testutils/testcluster", | ||
"//pkg/util/leaktest", | ||
"//pkg/util/randutil", | ||
], | ||
) | ||
|
||
get_x_data(name = "get_x_data") |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.