Fix wrong timestamp in log message (#1180) #1181
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Yu Lei <[email protected]>
Signed-off-by: Yu Lei <[email protected]>
ti-srebot
added
CHERRY-PICK
solotzg
approved these changes
Oct 23, 2020
|
/merge |
ti-srebot
added
the
status/can-merge
|
/run-all-tests |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
cherry-pick #1180 to release-4.0
Signed-off-by: Yu Lei [email protected]
What problem does this PR solve?
Problem Summary:
Milliseconds part of timestamp is wrong.
What is changed and how it works?
What's Changed:
How it Works:
Related changes
pingcap/docs/pingcap/docs-cn:Check List
Tests
Release note