statistics: fix the test case by increase the time interval #51139
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.
What problem does this PR solve?
Issue Number: close #51142
Problem Summary:
What changed and how does it work?
We received some unstable test reports regarding certain cases. The instability arose from the fact that the case attempted to verify if the job had failed just by now. However, in some instances, if the test case was running slowly, it wouldn't be considered as just failing now because it is more than one second. To address this, we decided to omit the fail reason check in this PR. Additionally, we changed the timer intervals from 1 second to 10 seconds.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.