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

cmd/objdump: fail on windows-arm64-11 builder #58262

Closed
gopherbot opened this issue Feb 2, 2023 · 5 comments
Closed

cmd/objdump: fail on windows-arm64-11 builder #58262

gopherbot opened this issue Feb 2, 2023 · 5 comments
Assignees
@bcmills
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Go1.21

Comments

@gopherbot
Copy link

gopherbot commented Feb 2, 2023 •
edited by cherrymui 

#!watchflakes
post <- pkg == "cmd/objdump" && builder == "windows-arm64-11" && `exit status 1`

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestGoobjFileNumber (160.55s)
    exec.go:146: test timed out while running command: C:\workdir\go\bin\go.exe build -o C:\Users\gopher\AppData\Local\Temp\TestGoobjFileNumber3908628149\001\p.a
    objdump_test.go:359: build failed: exit status 1

— watchflakes
@gopherbot gopherbot added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. compiler/runtime Issues related to the Go compiler and/or runtime. labels Feb 2, 2023
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "cmd/objdump" && test == "TestGoobjFileNumber"
2023-01-31 18:47 windows-arm64-11 go@bb4ea80b cmd/objdump.TestGoobjFileNumber (log) 
--- FAIL: TestGoobjFileNumber (160.55s)
    exec.go:146: test timed out while running command: C:\workdir\go\bin\go.exe build -o C:\Users\gopher\AppData\Local\Temp\TestGoobjFileNumber3908628149\001\p.a
    objdump_test.go:359: build failed: exit status 1

— watchflakes

@cherrymui
Copy link
Member

Probably related to #58219 , which is closed now. Closing for now.

@cherrymui cherrymui mentioned this issue Feb 2, 2023
Closed
@cherrymui cherrymui changed the title cmd/objdump: TestGoobjFileNumber failures cmd/objdump: fail on windows-arm64-11 builder Feb 2, 2023
@bcmills
Copy link
Contributor

bcmills commented Feb 2, 2023

I think it might actually be a variant of #58248 / #56967.

@cherrymui cherrymui mentioned this issue Feb 2, 2023
Closed
@bcmills bcmills self-assigned this Feb 2, 2023
@bcmills bcmills added this to the Go1.21 milestone Feb 2, 2023
@cherrymui
Copy link
Member

cherrymui commented Feb 2, 2023 •
edited

I think it is more like #58219. There are a few failures on objdump tests around the same time as the disk space failure.
Also, a new failure https://build.golang.org/log/5bbd1b66b0b381a688f45edf43d4d57c38d2283c, which is objdump and disk space (which seems the disk space issue comes back again?)

@cherrymui
Copy link
Member

It could also be a combination: rebuilding the std caused it to use more disk space. So fixing the rebuild would also have an effect.

@golang golang locked and limited conversation to collaborators Feb 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bcmills bcmills

Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Test Flakes
Status: Done
Milestone
Go1.21
Development

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