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.

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

x/exp/maps: failures with "cannot infer M1" since 2022-03-01 #51440

Closed
bcmills opened this issue Mar 2, 2022 · 4 comments
Closed

x/exp/maps: failures with "cannot infer M1" since 2022-03-01 #51440

bcmills opened this issue Mar 2, 2022 · 4 comments
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker
Milestone
Go1.18

Comments

@bcmills
Copy link
Contributor

bcmills commented Mar 2, 2022 

# golang.org/x/exp/maps [golang.org/x/exp/maps.test]
maps/maps_test.go:55:10: cannot infer M2 (/var/folders/9w/4l2_g3kx01x199n37fbmv3s80000gn/T/workdir-host-darwin-10_14/gopath/src/golang.org/x/exp/maps/maps.go:30:16)
maps/maps_test.go:58:10: cannot infer M1 (/var/folders/9w/4l2_g3kx01x199n37fbmv3s80000gn/T/workdir-host-darwin-10_14/gopath/src/golang.org/x/exp/maps/maps.go:30:12)
maps/maps_test.go:95:14: cannot infer M2 (/var/folders/9w/4l2_g3kx01x199n37fbmv3s80000gn/T/workdir-host-darwin-10_14/gopath/src/golang.org/x/exp/maps/maps.go:44:30)
maps/maps_test.go:98:14: cannot infer M1 (/var/folders/9w/4l2_g3kx01x199n37fbmv3s80000gn/T/workdir-host-darwin-10_14/gopath/src/golang.org/x/exp/maps/maps.go:44:16)
maps/maps_test.go:129:11: cannot infer M2 (/var/folders/9w/4l2_g3kx01x199n37fbmv3s80000gn/T/workdir-host-darwin-10_14/gopath/src/golang.org/x/exp/maps/maps.go:30:16)

greplogs --dashboard -md -l -e 'maps/maps_test\.go:\d+:\d+: cannot infer M[12]'

2022-03-02T11:49:04-77fc55f-40e24a9/darwin-amd64-10_14
2022-03-02T11:49:04-77fc55f-40e24a9/darwin-amd64-10_15
2022-03-02T11:49:04-77fc55f-40e24a9/darwin-amd64-11_0
2022-03-02T11:49:04-77fc55f-40e24a9/darwin-amd64-12_0
2022-03-02T11:49:04-77fc55f-40e24a9/darwin-arm64-11_0-toothrot
2022-03-02T11:49:04-77fc55f-40e24a9/darwin-arm64-12_0-toothrot
2022-03-02T11:49:04-77fc55f-40e24a9/linux-amd64
2022-03-02T11:49:04-77fc55f-40e24a9/linux-amd64-longtest
2022-03-02T11:49:04-77fc55f-40e24a9/linux-amd64-nocgo
2022-03-02T11:49:04-77fc55f-40e24a9/linux-amd64-race
2022-03-02T11:33:18-77fc55f-fd2e1e7/darwin-amd64-10_15
2022-03-02T11:33:18-77fc55f-fd2e1e7/darwin-amd64-11_0
2022-03-02T11:33:18-77fc55f-fd2e1e7/darwin-amd64-12_0
2022-03-02T11:33:18-77fc55f-fd2e1e7/darwin-arm64-11_0-toothrot
2022-03-02T11:33:18-77fc55f-fd2e1e7/darwin-arm64-12_0-toothrot
2022-03-02T11:33:18-77fc55f-fd2e1e7/linux-amd64
2022-03-02T11:33:18-77fc55f-fd2e1e7/linux-amd64-longtest
2022-03-02T11:33:18-77fc55f-fd2e1e7/linux-amd64-nocgo
2022-03-02T11:33:18-77fc55f-fd2e1e7/linux-amd64-race
2022-03-02T11:28:40-77fc55f-bebe9aa/darwin-amd64-10_14
2022-03-02T11:28:40-77fc55f-bebe9aa/darwin-amd64-10_15
2022-03-02T11:28:40-77fc55f-bebe9aa/darwin-amd64-11_0
2022-03-02T11:28:40-77fc55f-bebe9aa/darwin-amd64-12_0
2022-03-02T11:28:40-77fc55f-bebe9aa/linux-amd64
2022-03-02T11:28:40-77fc55f-bebe9aa/linux-amd64-longtest
2022-03-01T23:49:01-77fc55f-6da16b6/darwin-amd64-10_14
2022-03-01T23:49:01-77fc55f-6da16b6/darwin-amd64-10_15
2022-03-01T23:49:01-77fc55f-6da16b6/darwin-amd64-11_0
2022-03-01T23:49:01-77fc55f-6da16b6/darwin-amd64-12_0
2022-03-01T23:49:01-77fc55f-6da16b6/darwin-arm64-11_0-toothrot
2022-03-01T23:49:01-77fc55f-6da16b6/darwin-arm64-12_0-toothrot
2022-03-01T23:49:01-77fc55f-6da16b6/linux-amd64
2022-03-01T23:49:01-77fc55f-6da16b6/linux-amd64-longtest
2022-03-01T23:49:01-77fc55f-6da16b6/linux-amd64-nocgo
2022-03-01T23:49:01-77fc55f-6da16b6/linux-amd64-race
@gopherbot gopherbot added this to the Unreleased milestone Mar 2, 2022
@bcmills
Copy link
Contributor Author

bcmills commented Mar 2, 2022

Marking as release-blocker for Go 1.18. This affects generics (a top-line 1.18 feature) and x/exp/maps (a key library for users to try out generics), and was introduced very recently. (It's also nominally a release-blocker via #11811, because these tests are failing persistently.)

CC @golang/release

@bcmills bcmills added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker labels Mar 2, 2022
@bcmills bcmills modified the milestones: Unreleased, Go1.18 Mar 2, 2022
@bcmills
Copy link
Contributor Author

bcmills commented Mar 2, 2022

The first failure in the logs was at CL 388294 (attn @griesemer @findleyr).

@griesemer
Copy link
Contributor

See #51438.

@griesemer griesemer self-assigned this Mar 2, 2022
@bcmills
Copy link
Contributor Author

bcmills commented Mar 2, 2022

Duplicate of #51438

@bcmills bcmills marked this as a duplicate of #51438 Mar 2, 2022
@bcmills bcmills closed this as completed Mar 2, 2022
@golang golang locked and limited conversation to collaborators Jun 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker
Projects
None yet
Milestone
Go1.18
Development

No branches or pull requests
3 participants
@bcmills @griesemer @gopherbot