Skip to content

Triage remaining gorepo test failures in 1.18 #1131

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

Merged
merged 6 commits into from
Jul 27, 2022

Conversation

nevkontakte
Copy link
Member

A short summary of changes:

  • 3 tests are skipped because they are testing features specific to the upstream compiler.
  • 1 test is related to unsafe package. We could support it in future, but it's not a trivial fix, and it isn't a new regression. I filed a separate issue for this.
  • 1 test fails because gopherjs has numerous issues with defer/recover handling, which differ subtly from the Go spec. This isn't a new regression either, so I filed an issue for it too.
  • 1 test used to fail but is now passing, and I marked it as such.

At this point all CI should be green and the only major TODOs are supporting test-like execution of fuzz tests and generics.

Updates #1092.

  - fixedbugs/issue46938.go tests checkptr mode, which is unapplicable
    to GopherJS.
  - fixedbugs/issue47928.go tests //go:nointerface pragma, which is not
    a part of the Go spec.
  - fixedbugs/issue49665.go will be re-enabled in Go 1.19, where -G=3
    flag is removed; it would have passed if not for the unsupported
    flag.
This isn't a new regression in Go 1.18 and there seem to be several
distinct bugs affecting it, so it's reasonable to address it as a
separate issue: gopherjs#1128.
Although we could support this function, we currently do not and the
`unsafe` package generally has limited support status.

Filed gopherjs#1130 to track this.
@nevkontakte nevkontakte requested a review from flimzy July 26, 2022 18:49
@nevkontakte nevkontakte merged commit 405ff02 into gopherjs:go1.18 Jul 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants