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

cmd/dist: "unexpected stale targets" on linux-ppc64le-power9osu builder #35749

Closed
bcmills opened this issue Nov 21, 2019 · 5 comments
Closed

cmd/dist: "unexpected stale targets" on linux-ppc64le-power9osu builder #35749

bcmills opened this issue Nov 21, 2019 · 5 comments

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented Nov 21, 2019

@bcmills bcmills added this to the Backlog milestone Nov 21, 2019
@laboger
Copy link
Contributor

@laboger laboger commented Nov 21, 2019

I will try to reproduce the problem. I also agree it is curious that it only happens on the power9 builder, which has happened with other intermittent failures too.

I don't know if this is possible but if somehow the value for objabi.GOPPC64 is not set to power9 before all compiles start, and some are compiled for power8 but rebuilt later for power9 then the hashes wouldn't match.

@laboger
Copy link
Contributor

@laboger laboger commented Nov 21, 2019

The errlogs look strange, almost like the build hasn't even started yet. It doesn't display the line that says it is building go_bootstrap or even the one that provides the detail about the test run.

@laboger
Copy link
Contributor

@laboger laboger commented Nov 21, 2019

I found that the old power9 builder was still active out in the farm (not running Docker). Not sure but maybe these errors were happening if that buildlet was being used, since the error happened intermittently. Carlos has shut down that buildlet and we will see if that makes a difference.

@laboger
Copy link
Contributor

@laboger laboger commented Nov 22, 2019

I think that was the problem. Now that the old buildlet isn't running, I am not seeing the error. When it did happen, it was failing every 5 or 6 runs which would make sense since that was the 6th one in the pool.

@bcmills
Copy link
Member Author

@bcmills bcmills commented Nov 22, 2019

Great, thank you!

I'll close this out; we can always reopen it if the problem isn't actually gone.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.