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/link/internal/ld: TestArchiveBuildInvokeWithExec flaky on Darwin builders #35542

Open
bcmills opened this issue Nov 12, 2019 · 4 comments
Open

Comments

@jeremyfaller
Copy link
Contributor

@jeremyfaller jeremyfaller commented Nov 12, 2019

The 11-04 failures were addressed by @cherrymui in 205278. Than might be the best to address the most recent one, but if it's a single failure, I could see it being a flaky.

Loading

@ianlancetaylor
Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Nov 16, 2019

No new occurrences. I'm calling this one fixed. Let's reopen if we see it again.

Loading

@bcmills
Copy link
Member Author

@bcmills bcmills commented Mar 27, 2020

Loading

@bcmills bcmills reopened this Mar 27, 2020
@ALTree ALTree removed this from the Go1.14 milestone Jul 22, 2020
@ALTree ALTree added this to the Go1.16 milestone Jul 22, 2020
@aclements
Copy link
Member

@aclements aclements commented Dec 7, 2020

Filtering out the "duplicate symbol" failures from 11-04, we have just two failures that look the same as each other:

$ greplogs -dashboard -E "FAIL: TestArchiveBuildInvokeWithExec" -E "invoking archiver" -l -md
2020-03-26T17:48:20-918d4d4/darwin-amd64-10_12
2019-11-12T01:09:40-c2edcf4/darwin-amd64-10_11

Given how rare this seems to be, it's hard to statistically say whether this even seems to be fixed. I'm going to kick this to Unplanned.

Loading

@aclements aclements removed this from the Go1.16 milestone Dec 7, 2020
@aclements aclements added this to the Unplanned milestone Dec 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants