[UT] Fix unstable ut for Restore cause by @Mocked annotation for SystemInfoService (backport #60078) #60083
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.
Why I'm doing:
Missing 1 invocation to:
will be throw when running the RestoreJobTest for some SystemInfoService stackThe reason is the SystemInfoService object has the
@Mocked
annotation which means all member functions are not mentioned inExpectations{}
should not be called in the UT. But some background thread will call such functions and get unexpected exception.@Mocked
annotation will affect the Class itself, so even a new object is new in another thread, it still be affected by the rule.What I'm doing:
New a object for SystemInfoService and use partial mocking for jmockit.
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #60078 done by [Mergify](https://mergify.com).