*: fix flaky test TestPreparingProgress and TestRemovingProgress#9465
*: fix flaky test TestPreparingProgress and TestRemovingProgress#9465ti-chi-bot[bot] merged 9 commits intotikv:masterfrom
TestPreparingProgress and TestRemovingProgress#9465Conversation
Signed-off-by: okJiang <819421878@qq.com>
|
Skipping CI for Draft Pull Request. |
|
/retest |
4 similar comments
|
/retest |
|
/retest |
|
/retest |
|
/retest |
Signed-off-by: okJiang <819421878@qq.com>
Signed-off-by: okJiang <819421878@qq.com>
|
/retest |
1 similar comment
|
/retest |
Signed-off-by: okJiang <819421878@qq.com>
Signed-off-by: okJiang <819421878@qq.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #9465 +/- ##
=======================================
Coverage 76.18% 76.19%
=======================================
Files 481 481
Lines 75517 75541 +24
=======================================
+ Hits 57534 57556 +22
- Misses 14419 14420 +1
- Partials 3564 3565 +1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
server/cluster/cluster.go
Outdated
| if !readyToServe && (c.IsPrepared() || (c.IsServiceIndependent(constant.SchedulingServiceName) && c.isStorePrepared())) { | ||
| threshold = c.getThreshold(stores, store) | ||
| log.Debug("store preparing threshold", zap.Uint64("store-id", storeID), | ||
| log.Info("store preparing threshold", zap.Uint64("store-id", storeID), |
There was a problem hiding this comment.
This will be revert before pr merge.
|
|
||
| // TestSwitchBurst is used to test https://github.com/tikv/pd/issues/6209 | ||
| func (suite *resourceManagerClientTestSuite) TestSwitchBurst() { | ||
| suite.T().Skip("skip this test because it is not stable") |
There was a problem hiding this comment.
when will we open it again?
There was a problem hiding this comment.
Maybe after someone fixes it😂
Signed-off-by: okJiang <819421878@qq.com>
|
/retest |
Signed-off-by: okJiang <819421878@qq.com>
|
/retest |
|
How about adding some descriptions for the reason? |
Here we wait for a For TestPreparingProgress, let's take this as an example https://github.com/tikv/pd/actions/runs/16019981411/job/45194384196 This is because after checkStoresLoop, the store may have entered the preparing state, so it may fail. Therefore, we need to block checkStores to obtain the intermediate state. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lhy1024, rleungx The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
1 similar comment
|
/retest |
|
/test pull-build pull-build-next-gen |
What problem does this PR solve?
Issue Number: Close #9461,
What is changed and how does it work?
Here we wait for a
checkStoresinterval to trigger the progress manager logic to get the removing status.For TestPreparingProgress, let's take this as an example https://github.com/tikv/pd/actions/runs/16019981411/job/45194384196
This is because after checkStoresLoop, the store may have entered the preparing state, so it may fail. Therefore, we need to block checkStores to obtain the intermediate state.
Check List
Tests
Release note