-
Notifications
You must be signed in to change notification settings - Fork 828
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
add log for resourceinterpreter_test #3859
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## master #3859 +/- ##
==========================================
- Coverage 55.18% 55.18% -0.01%
==========================================
Files 227 227
Lines 21658 21678 +20
==========================================
+ Hits 11953 11963 +10
- Misses 9069 9078 +9
- Partials 636 637 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
e0d6493
to
6645b88
Compare
Signed-off-by: chaosi-zju <chaosi@zju.edu.cn>
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.
Thanks~
the problem has been fixed by #3909 |
@chaosi-zju: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What type of PR is this?
/kind flake
What this PR does / why we need it:
add little log to debug issue
Which issue(s) this PR fixes:
#3825
Special notes for your reviewer:
@XiShanYongYe-Chang @RainbowMango
Does this PR introduce a user-facing change?:
none