-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
disable an unstable test case #3600
Conversation
@@ -219,64 +219,60 @@ TEST(ChainDeleteEdgesTest, Test4) { | |||
std::this_thread::sleep_for(std::chrono::milliseconds(300)); | |||
} | |||
|
|||
// add some edges, then delete one of them, not execute local commit | |||
TEST(ChainDeleteEdgesTest, Test5) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
use DISABLE_Test5 to disable this test case
5b7a027
@@ -271,9 +236,9 @@ TEST(ChainDeleteEdgesTest, Test5) { | |||
FakeInternalStorageClient::hookInternalStorageClient(env, iClient); | |||
ChainResumeProcessor resumeProc(env); | |||
resumeProc.process(); | |||
// std::this_thread::sleep_for(std::chrono::milliseconds()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why don't remove directly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is just for not cause other CI failed. Will dig more until it stable.
Thus it will have some debug code. Not sure if this is the unstable point.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could convert it to a draft PR.
What type of PR is this?
What does this PR do?
It is reported some CI failed of chain_delete_test.Test5
can't repro on 211, just disable it for a while.
(It is weird that test5 and test6 is almost same... why test 6 not failed???)
Which issue(s)/PR(s) this PR relates to?
Special notes for your reviewer, ex. impact of this fix, etc:
Additional context/ Design document:
Checklist:
Release notes:
Please confirm whether to be reflected in release notes and how to describe: