util: introduce tracing-based test toolkit#22434
util: introduce tracing-based test toolkit#22434lysu wants to merge 2 commits intopingcap:masterfrom lysu:dev-2pc-trace-test
Conversation
|
No release note, Please follow https://github.com/pingcap/community/blob/master/contributors/release-note-checker.md |
Signed-off-by: lysu <sulifx@gmail.com>
|
/rebuild |
Signed-off-by: lysu <sulifx@gmail.com>
|
The core part are those three operation:
And then
Sandbox is used to manage the whole thing, it bind each goroutine with context, each goroutine can get its |
|
@lysu: PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: lysu sulifx@gmail.com
What problem does this PR solve?
Problem Summary:
failpoint is powerful, but it's still not easy to write testcase to simulate multiple routines' execution in white-box test.
this simple PR just want to let testcase can control execution path like using "programmable-debugger"(try delve but failed)
and take benefit from opentracing, it support "assert opentracing log" like "assert explain result"
IMHO, it maybe useful to write whitebox-testcast to simulate conflict or event happen in different routines as different order.
What is changed and how it works?
What's Changed, How it Works:
also write 2 testcase demo in 1pc_test and 2pc_test
Related changes
Check List
Tests
Side effects
Release note
This change is