Skip to content

fixedbugs/issue48898.go is failing on gopherjs #1128

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.

Sign up for GitHub

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

Jump to bottom
Open
nevkontakte opened this issue Jul 17, 2022 · 2 comments
Open

fixedbugs/issue48898.go is failing on gopherjs #1128

nevkontakte opened this issue Jul 17, 2022 · 2 comments
Assignees
@SnoozeThis
Labels
bug
Milestone
Go spec compliance

Comments

@nevkontakte
Copy link
Member

The upstream test case added in Go 1.18 for golang/go#48898 is failing in gopherjs too. However, it appears the root cause is different, or at least is masked by #1126 and/or #1127.

I have disabled that test until both issues above are resolved. We should re-visit this issue afterwards.
@nevkontakte
Copy link
Member Author

@SnoozeThis #1126 && #1127 -> assign to @nevkontakte

@SnoozeThis
Copy link

(https://snoozeth.is/NIphOSk9RPQ) I will wait until #1126 is closed and wait until #1127 is closed and then assign to @nevkontakte.

@nevkontakte nevkontakte added this to the Go spec compliance milestone Jul 17, 2022
nevkontakte added a commit to nevkontakte/gopherjs that referenced this issue Jul 21, 2022
@nevkontakte
Skip fixedbugs/issue48898.go
68505dc 
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SnoozeThis SnoozeThis

Labels
bug
Projects
None yet
Milestone
Go spec compliance
Development

No branches or pull requests
2 participants
@nevkontakte @SnoozeThis