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.

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/link: "readSym out of sync" flake #33863

Open
bcmills opened this issue Aug 27, 2019 · 7 comments
Open

cmd/link: "readSym out of sync" flake #33863

bcmills opened this issue Aug 27, 2019 · 7 comments
Labels
Builders x/build issues (builders, bots, dashboards) compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Unplanned

Comments

@bcmills
Copy link
Contributor

bcmills commented Aug 27, 2019 •
edited

Observed in the darwin-amd64-10_14 in https://build.golang.org/log/2c4dfc954904829f5c15825b108b5d21e2108fe4:

# go/token.test
2019/08/26 10:19:55 readSym out of sync
ok  	go/printer	0.213s
ok  	go/scanner	0.013s
FAIL	go/token [build failed]

That line comes from here:

go/src/cmd/link/internal/objfile/objfile.go

Line 213 in 1a423be

log.Fatalln("readSym out of sync")

@bcmills bcmills added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Aug 27, 2019
@bcmills bcmills added this to the Unplanned milestone Aug 27, 2019
@bcmills
Copy link
Contributor Author

bcmills commented Aug 27, 2019

CC @cherrymui @jeremyfaller

@cherrymui
Copy link
Member

This looks to me like, if not a memory corruption, the object file is corrupted. Is it possible to retrieve the object file from the builder in case of a failure?

Object file corruption would also explain other flaky linker crashes on the darwin builders. Could it be, by any chance, that the darwin builders' file system is less stable?

@bcmills bcmills added the Builders x/build issues (builders, bots, dashboards) label Aug 27, 2019
@bcmills
Copy link
Contributor Author

bcmills commented Aug 27, 2019

Could it be, by any chance, that the darwin builders' file system is less stable?

Maybe! (CC @bradfitz @toothrot @dmitshur for builder info.)

@bradfitz
Copy link
Contributor

That seems very unlikely.

It's a fresh VMware VM per build, with the VM disk storage on a fancy SSD storage array.

@toothrot
Copy link
Contributor

Is it possible that r.readByte() is returning an error in this failure? It looks like we're not logging it, regardless.

@bradfitz
Copy link
Contributor

Yeah, I'd start with improving the failure message.

@ert485
Copy link

ert485 commented May 16, 2020

I hit this message on a Raspberry Pi Zero.
(go1.11.6 linux/arm)
After a reboot I got errors that looked like: /home/pi/.cache/go-build/63/638e72...-d(3): not an object file
I cleared the cache with rm -rf /home/pi/.cache, then it built fine

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Builders x/build issues (builders, bots, dashboards) compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
6 participants
@bradfitz @toothrot @bcmills @ert485 @gopherbot @cherrymui