-
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.
49397: roachtest: run EXPLAIN ANALYZE when tpchvec/perf fails r=yuzefovich a=yuzefovich **workload: switch TPCH queries mapping from using string to int** It also exports `NumQueries` and `QueriesByNumber` fields of `tpch` package to be used by `tpchvec` roachtest. Release note: None **roachtest: minor cleanup of tpchbench** This commit refactors `tpchbench` test slightly in order to hide `tpch` bench type from the whole `roachtest` package. Release note: None **roachtest: run EXPLAIN ANALYZE when tpchvec/perf fails** We have a mysterious rare failure on query 7 in which `vectorize=on` performs significantly worse than `vectorize=off`. I'm out of possible explanations for this, so this commit adds an ability to run `EXPLAIN ANALYZE` on the query with both `vectorize` options when the slowness threshold is exceeded. Hopefully it'll give us some insight into the perf failures. Addresses: #47401. Release note: None 49429: *: replace test usages of context.TODO() with context.Background() r=otan a=otan *: replace test usages of context.TODO() with context.Background() This commit replaces all usages of context.TODO() with context.Background() in tests, and adds a lint rule ensuring context.TODO() does not appear. Tests should always be initiating a new context if they are calling a function for the first time - it is now "unknown" and hence not a "TODO" application. Also added a new test in `lint_test.go` for this. Release note: None Co-authored-by: Yahor Yuzefovich <[email protected]> Co-authored-by: Oliver Tan <[email protected]>
- Loading branch information
Showing
227 changed files
with
1,602 additions
and
1,566 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
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.