Open YangKeao opened 2 weeks ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
/retest
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
/retest
/retest
Attention: Patch coverage is 15.15152%
with 84 lines
in your changes are missing coverage. Please review.
Project coverage is 74.6350%. Comparing base (
0afe54d
) to head (740ccd3
). Report is 1 commits behind head on master.
/retest
[FORMAT CHECKER NOTIFICATION]
Notice: To remove the do-not-merge/needs-tests-checked
label, please finished the tests then check the finished items in description.
For example:
Tests
- [x] Unit test
- [ ] Integration test
- [ ] Manual test (add detailed scripts or steps below)
- [ ] No code
:open_book: For more info, you can check the "Contribute Code" section in the development guide.
/retest
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign windtalker, winoros, zimulala for approval, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.
The full list of commands accepted by this bot can be found here.
@YangKeao: The following test failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
fast_test_tiprow | 740ccd3d37fe4a662ac131750d37008f0b280200 | link | true | /test fast_test_tiprow |
Full PR test history. Your PR dashboard.
@YangKeao: The following test failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
idc-jenkins-ci-tidb/unit-test | 740ccd3d37fe4a662ac131750d37008f0b280200 | link | true | /test unit-test |
Full PR test history. Your PR dashboard.
What problem does this PR solve?
Issue Number: close #53336
Problem Summary:
It's not safe to call
Next
(or other method) of an executor after the session is executing the next statement. We have split out a lot ofContext
and it's clear that the context depended by theTableReaderExecutor
is safe to be re-used (after proper configuration) while executing another statement is running on the session.What changed and how does it work?
This PR adds
IntoStatic
method for several contexts. After calling this method, the context can be safe to be used while the session continues to run the next statements.Check List
Tests
TODO:
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.