Skip to content

../test: tests consistently failing with -G=0 on longtest builders #50159

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
Closed
bcmills opened this issue Dec 14, 2021 · 1 comment
Closed

../test: tests consistently failing with -G=0 on longtest builders #50159

bcmills opened this issue Dec 14, 2021 · 1 comment
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker Soon This needs action soon. (recent regressions, service outages, unusual time-sensitive situations)
Milestone
Go1.18

Comments

@bcmills
Copy link
Contributor

bcmills commented Dec 14, 2021

../test is failing as of CL 368254 on the -longtest builders.

Note that the behavior of the tests in that directory intentionally differ when run on the builders:
https://cs.opensource.google/go/go/+/master:test/run.go;l=88-94;drc=c1c303f6f8b77d3ed4e135583f3d60b159907245

You can reproduce these failures by running export GO_BUILDER_NAME=linux-amd64-longtest before all.bash.

greplogs --dashboard -md -l -e 'undefined: any' --since=2021-12-01

2021-12-14T01:48:22-1afa432/linux-386-longtest
2021-12-14T01:48:22-1afa432/linux-amd64-longtest
2021-12-14T01:48:22-1afa432/windows-amd64-longtest
2021-12-14T01:18:43-006d4e6/linux-386-longtest
2021-12-14T01:18:43-006d4e6/linux-amd64-longtest
2021-12-14T01:18:43-006d4e6/windows-amd64-longtest
2021-12-13T22:45:26-5b9207f/linux-386-longtest
2021-12-13T22:45:26-5b9207f/linux-amd64-longtest
2021-12-13T22:45:26-5b9207f/windows-amd64-longtest
2021-12-13T22:42:08-67917c3/linux-386-longtest
2021-12-13T22:42:08-67917c3/linux-amd64-longtest
2021-12-13T22:42:08-67917c3/windows-amd64-longtest
2021-12-13T21:29:11-9e85dc5/linux-386-longtest
2021-12-13T21:29:11-9e85dc5/linux-amd64-longtest
2021-12-13T21:29:11-9e85dc5/windows-amd64-longtest
2021-12-13T19:40:29-7bdbc73/windows-amd64-longtest
2021-12-13T19:08:31-3e8aa5d/windows-amd64-longtest
2021-12-13T18:55:52-f909f81/windows-amd64-longtest
2021-12-13T18:45:54-2580d0e/windows-amd64-longtest
@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 Dec 14, 2021
@bcmills bcmills added this to the Go1.18 milestone Dec 14, 2021
@bcmills bcmills added the Soon This needs action soon. (recent regressions, service outages, unusual time-sensitive situations) label Dec 14, 2021
@gopherbot
Copy link
Contributor

Change https://golang.org/cl/371715 mentions this issue: cmd/compile: fix any in -G=0 mode

@golang golang locked and limited conversation to collaborators Dec 14, 2022
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 Soon This needs action soon. (recent regressions, service outages, unusual time-sensitive situations)
Projects
None yet
Milestone
Go1.18
Development

No branches or pull requests
2 participants
@bcmills @gopherbot