-
Notifications
You must be signed in to change notification settings - Fork 12
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
fix sort by createtime is not work #123
Conversation
@lysign: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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. |
Codecov Report
@@ Coverage Diff @@
## master #123 +/- ##
=======================================
Coverage 47.46% 47.46%
=======================================
Files 6 6
Lines 552 552
Branches 152 152
=======================================
Hits 262 262
Misses 227 227
Partials 63 63 |
Signed-off-by: liuying <liu.ying@99cloud.net>
/lgtm |
LGTM label has been added. Git tree hash: 9a69a399c581cff0d90947220b5ae0d4b6fb51d2
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lysign, moweiwei The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cherrypick release-1.1 |
@moweiwei: new pull request created: #126 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. |
Signed-off-by: liuying liu.ying@99cloud.net
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #107
Special notes for reviewers:
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: