-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
*: upgrade go 1.20.1 #40965
*: upgrade go 1.20.1 #40965
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
7be9ba9
to
3e1dd69
Compare
/retest |
/test check-dev2 |
parser/terror/terror_test.go
Outdated
@@ -142,7 +142,7 @@ func TestTraceAndLocation(t *testing.T) { | |||
sysStack++ | |||
} | |||
} | |||
require.Equalf(t, 11, len(lines)-(2*sysStack), "stack =\n%s", stack) | |||
require.Equalf(t, 13, len(lines)-(2*sysStack), "stack =\n%s", stack) |
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.
Could you check the stack of the error stack? I just curious what the changes look like.
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.
we use bazel to run tests and bazel will manage Golang environment so that we find the stack path is different from running with gotest
.
I have added a comment in the code to describe this problem.
/retest |
1 similar comment
/retest |
3efb4da
to
a5a21f2
Compare
/retest |
a5a21f2
to
dfc7d75
Compare
/retest |
dfc7d75
to
bd26fd3
Compare
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.
LGTM
/retest |
Signed-off-by: Weizhen Wang <wangweizhen@pingcap.com>
Signed-off-by: Weizhen Wang <wangweizhen@pingcap.com>
Signed-off-by: Weizhen Wang <wangweizhen@pingcap.com>
bd26fd3
to
62e316c
Compare
util/misc.go
Outdated
if inval.Reason != x509.Expired { | ||
return false | ||
} | ||
case *tls.CertificateVerificationError: |
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.
It is relation with go1.20
.
For a handshake failure due to a certificate verification failure, the TLS
client and server now return an error of the new type
CertificateVerificationError, which includes the presented certificates.
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.
Although we use bazel to build/test code with go1.20, we have some tasks with go1.19. I have to skip this test after all upgrading the go1.20
/merge |
This pull request has been accepted and is ready to merge. Commit hash: d14e81b
|
// ``` | ||
// | ||
// So we have to deal with these boundary conditions. | ||
if strings.Contains(line, goroot) || strings.Contains(line, "GOROOT") || strings.Contains(line, "runtime.goexit") { | ||
sysStack++ |
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.
I don't use gvm and my stack looks like
...
testing.tRunner
/usr/lib/go/src/testing/testing.go:1576
runtime.goexit
/usr/lib/go/src/runtime/asm_amd64.s:1598
The last two lines will be counted twice, because /usr/lib/go/src/runtime/asm_amd64.s:1598
also contains goroot
, thus make the test fail.
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.
Let me take a look.
Signed-off-by: Weizhen Wang wangweizhen@pingcap.com
What problem does this PR solve?
Issue Number: ref #40969
Problem Summary:
What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.