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

x/build: add linux-arm64-aws to the set of trybots #45065

Closed
cagedmantis opened this issue Mar 16, 2021 · 4 comments
Closed

x/build: add linux-arm64-aws to the set of trybots #45065

cagedmantis opened this issue Mar 16, 2021 · 4 comments

Comments

@cagedmantis
Copy link
Contributor

@cagedmantis cagedmantis commented Mar 16, 2021

As per our goals of including a trybot for any platform that can cause a release blocking issue (#29239), we will add linux-arm64-aws to the set of trybots. It should be able to complete runs under the trybot limit of 10 minutes. This new trybot will help alleviate an issue linked to host resources (#36170).

@golang/release @cherrymui

@gopherbot
Copy link

@gopherbot gopherbot commented Mar 19, 2021

Change https://golang.org/cl/303232 mentions this issue: dashboard: add linux-arm64-aws to set of trybots

@cagedmantis cagedmantis moved this from Planned to In Progress in Go Release Team Mar 23, 2021
Go Release Team automation moved this from In Progress to Done Apr 2, 2021
@bcmills
Copy link
Member

@bcmills bcmills commented May 24, 2021

This new TryBot is fairly flaky due to #41863.

Is someone planning to address that issue in the near term, or should the affected test(s) be skipped on the builder?

@dmitshur
Copy link
Contributor

@dmitshur dmitshur commented May 24, 2021

I think it makes sense to skip the affected tests as flaky, and keep that issue open.

@cagedmantis
Copy link
Contributor Author

@cagedmantis cagedmantis commented May 24, 2021

I agree. It would be great to get to the bottom of this though.

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

Successfully merging a pull request may close this issue.

None yet
4 participants