-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Silence retried to delete file messages #30974
Conversation
Backport |
Codecov Report
@@ Coverage Diff @@
## master #30974 +/- ##
=========================================
Coverage 62.3% 62.3%
Complexity 18208 18208
=========================================
Files 1142 1142
Lines 68176 68176
Branches 1232 1232
=========================================
Hits 42480 42480
Misses 25335 25335
Partials 361 361
Continue to review full report at Codecov.
|
@@ -272,7 +272,7 @@ public function openFile($name, Session $session) { | |||
* | |||
* @return void | |||
*/ | |||
public function deleteFile($name, Session $session, $maxRetries = STANDARDRETRYCOUNT) { | |||
public function deleteFile($name, Session $session, $expectToDeleteFile = true, $maxRetries = STANDARDRETRYCOUNT) { |
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.
long line makes it harder to review in GitHub
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.
reformat pushed
a44c44a
to
7656c98
Compare
7656c98
to
8d4a1c1
Compare
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
If the scenario step does not expect the file to be able to be deleted, then do not emit messages about "retried to delete". In this case we know that we are supposed to retry a bit, and then it is expected that we will give up and not be able to delete the file.
In this case, reduce the number of retries so we do not waste so much time rechecking that a delete really cannot be done.
Related Issue
#30897
This "cleanup" is to reduce "noise" in the test output, so that people do not mis-understand what is "normal" and what is a problem.
Motivation and Context
When a test tries to delete a file, and expects that it should not be possible to delete the file, then actually the "Delete" action does not exist in the file actions menu. That is expected and what is being tested for. But while doing the checks, the code emits messages like:
These are disturbing to read in the test output, and can send you off looking for problems in the wrong place, when actually this is expected to happen for these test scenario steps.
When we are doing this kind of "negative" "cannot delete" test, we should not emit this noise.
How Has This Been Tested?
Run a full set of webUI tests on Travis. Inspect the logs and see that these
INFORMATION:
messages no longer appear.Types of changes
Checklist: