Skip to content
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

test: split error message check to fix it for go 1.24 #4000

Merged
merged 1 commit into from
Oct 21, 2024

Conversation

mstoykov
Copy link
Contributor

What?

Fix a test in gotip/go1.24

Why?

as part of golang/go@0fe6347 now messages around encoding/json better specify the fields when embedding fields.

This does break a check on the message and the message will now be different between go versions.

With this commit the check is made to work between go versions.

Checklist

  • I have performed a self-review of my code.
  • I have added tests for my changes.
  • I have run linter locally (make lint) and all checks pass.
  • I have run tests locally (make tests) and all tests pass.
  • I have commented on my code, particularly in hard-to-understand areas.

Related PR(s)/Issue(s)

as part of golang/go@0fe6347
now messages around encoding/json better specify the fields when
embedding fields.

This does break a check on the message and the message will now be
different between go versions.

With this commit the check is made to work between go versions.
@mstoykov mstoykov added the tests label Oct 18, 2024
@mstoykov mstoykov added this to the v0.55.0 milestone Oct 18, 2024
@mstoykov mstoykov requested a review from a team as a code owner October 18, 2024 07:57
@mstoykov mstoykov requested review from oleiade and olegbespalov and removed request for a team October 18, 2024 07:57
@mstoykov mstoykov merged commit 844a496 into master Oct 21, 2024
23 checks passed
@mstoykov mstoykov deleted the fixGo1.24JSONError branch October 21, 2024 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants