Skip to content

access: may-start-trybots #66558

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

Closed
abner-chenc opened this issue Mar 27, 2024 · 5 comments
Closed

access: may-start-trybots #66558

abner-chenc opened this issue Mar 27, 2024 · 5 comments
Assignees
Labels
NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@abner-chenc
Copy link
Contributor

Hi,

I'd like to request the "may-start-trybots" access (https://go-review.googlesource.com/#/admin/groups/1030,members) for myself .

I'm already part of the @golang/loong64 team for a while, and I'll be helping gardening this port in the UTC+8 timezone for the foreseeable future. It's increasingly inconvenient to have to ping other people for TryBot runs as the number of outstanding loong64 CLs keeps growing.

See https://go.dev/wiki/GerritAccess

Thanks.

@abner-chenc abner-chenc added this to the Unreleased milestone Mar 27, 2024
@dmitshur dmitshur added the NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. label Mar 27, 2024
@dmitshur dmitshur added this to Access Mar 27, 2024
@github-project-automation github-project-automation bot moved this to Incoming in Access Mar 27, 2024
@dmitshur dmitshur moved this from Incoming to Active in Access Apr 5, 2024
@dmitshur dmitshur self-assigned this Apr 5, 2024
@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. labels Apr 5, 2024
@dmitshur
Copy link
Member

dmitshur commented Apr 5, 2024

Hi abner chenc,

Thanks for your contributions and helping maintain the linux/loong64 port. We've added you to the project-golang-may-start-trybots group, so you should be able to trigger trybots now.

As noted at https://go.dev/wiki/GerritAccess#running-trybots-may-start-trybots, please be sure to at least skim CLs for anything malicious before starting a trybot run.

Please let us know if you have any questions or issues. Thanks again.

@dmitshur dmitshur closed this as completed Apr 5, 2024
@github-project-automation github-project-automation bot moved this from Active to Done in Access Apr 5, 2024
@abner-chenc
Copy link
Contributor Author

I can't select tryjobs, do I need additional permissions? @dmitshur

@dmitshur
Copy link
Member

The gerrit account [email protected] is still present in the project-golang-may-start-trybots group, so you should be able to. Are you logged in with that account and following the directions described at https://go.dev/wiki/LUCI#trybots?

@abner-chenc
Copy link
Contributor Author

abner-chenc commented May 16, 2024

The gerrit account [email protected] is still present in the project-golang-may-start-trybots group, so you should be able to. Are you logged in with that account and following the directions described at https://go.dev/wiki/LUCI#trybots?

Yes,
When I click the ”CHOOSE TYRJOBS“ button to select one of the builders, such as gotip-linux-loong64, and click the “ADD” button, it fails, and an error message pops up saying "Failed to create builds. Please try again See console logs, too“, There is no other useful information left.

2024-05-16_23-39

@dmitshur
Copy link
Member

dmitshur commented May 16, 2024

To confirm, you are able to leave a Commit-Queue+1 vote using your account, is that right? I see here that is so.

In that case, the may-start-trybots access is successfully granted to your Gerrit account, but this appears to be something else going wrong when using the Gerrit UI. Please file a new issue with a prefix "gerrit: " so we can continue the investigation there. (Edit: Issue #67468 is filed now.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsFix The path to resolution is known, but the work has not been done.
Projects
Status: Reviewed
Development

No branches or pull requests

2 participants