roachtest: get exec traces in gossip/chaos/nodes=9 #135253
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This test is known for strange behavior (#134527).
A recent test failure1 shows that we "lose time"
in more unexpected locations.
I'm assuming an execution trace (of the roachtest process) will be
helpful here, as we'll be able to determine whether the time is
spent in roachtest or on the CockroachDB server side.
Epic: none
Release note: None
Footnotes
https://github.com/cockroachdb/cockroach/issues/135154 ↩