-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
kv/kvnemesis: TestValidate failed #110765
Comments
kv/kvnemesis.TestValidate failed with artifacts on master @ 6cbd07ee6fbfb92706e8cdc8c559960b1bc41663:
Parameters: |
kv/kvnemesis.TestValidate failed with artifacts on master @ 6cbd07ee6fbfb92706e8cdc8c559960b1bc41663:
Parameters: |
Bisected to 6dc61d5. |
I'm confused; do Cockroach tests build Pebble with the |
I think the invariants checks are also enabled under |
I can reproduce this using a race build using the following command: I wasn't able to reproduce without the --race flag. Thankfully, it fails easily without the --stress flag. Bisected to the following Pebble commit: cockroachdb/pebble@529d256 Edit: |
I think the problem might be here: https://github.com/cockroachdb/cockroach/blob/master/pkg/kv/kvnemesis/validator.go#L1385. The tests pass if I copy the |
110693: sql: wrap each planNode into DistSQL independently when collecting stats r=yuzefovich a=yuzefovich This commit adjusts the DistSQL physical planner to create a pair of `planNodeToRowSource` and `rowSourceToPlanNode` for each `planNode` whenever it's included into the DistSQL flow separately whenever the execution statistics are collected. This allows us to collect exec stats for each plan node (rather than see the execution time of the whole chain of `planNode`s and the number of output rows only of the first `planNode` to be wrapped). This should have negligible overhead. The only exception for when this wrapping is disabled is when the planNode implements `batchedPlanNode` interface since wrapping those types of planNodes breaks some assumptions. This was useful in a recent query latency investigation where multiple virtual table lookup joins (powered by the corresponding planNodes) were taking vast majority of the query execution, but since all of them were hidden behind a single pair of DistSQL adapters, it wasn't clear which particular vtable lookup join was the bottleneck. Epic: None Release note: None 110863: kv/kvnemesis: copy value before holding a reference r=bananabrick a=bananabrick Epic: none Fixes: #110765 Co-authored-by: Yahor Yuzefovich <[email protected]> Co-authored-by: Arjun Nair <[email protected]>
kv/kvnemesis.TestValidate failed with artifacts on master @ 985662236d7bf273b93a7b5e32def8e2d1043640:
Fatal error:
Stack:
Log preceding fatal error
Parameters:
TAGS=bazel,gss
,stress=true
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-31598
The text was updated successfully, but these errors were encountered: