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

gerrit: unable to select specific builder to execute tryjobs via "Choose tryjobs" dialog's Add button #67468

Open
abner-chenc opened this issue May 17, 2024 · 2 comments
Labels
DevExp anything around developer experience NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@abner-chenc
Copy link
Contributor

abner-chenc commented May 17, 2024

Hi, @dmitshur :

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.

I have confirmed that my account "chenguoqi@loongson.cn" can perform Commit-Queue+1. Here are the results of my Commit-Queue+1.

  • Here are my steps:

2024-05-17_19-13

  • Here is my login account

2024-05-17_19-17

@dmitshur dmitshur added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. DevExp anything around developer experience labels May 17, 2024
@dmitshur dmitshur added this to the Unreleased milestone May 17, 2024
@dmitshur
Copy link
Contributor

dmitshur commented May 17, 2024

Thanks for reporting. CC @golang/release.

First, can you try and see if you're able to start slowbots by including a Cq-Include-Trybots: luci.golang.try:gotip-linux-loong64 git footer in the commit message, as documented in the "Blocking" bullet point of https://go.dev/wiki/SlowBots#using-slowbots. If that works, that'll confirm that workaround is available, and that this problem is to do with the frontend UI of Gerrit.

Second, the error message suggests to see browser console logs, can you see if there's a relevant error message there that might help explain this?

I suspect there's something going wrong with the Gerrit UI frontend that triggers the API call when you press the "Add" button. It's unclear why it only affects that dialog and not others. But Gerrit has a button in the top right corner to report a bug, which might be the best path forward if we confirm this only affects the dialog and not the Cq-Include-Trybots approach to triggering slowbots.

@dmitshur dmitshur changed the title gerrit: Unable to select specific builder to execute tryjobs gerrit: unable to select specific builder to execute tryjobs via "Choose tryjobs" dialog's Add button May 17, 2024
@abner-chenc
Copy link
Contributor Author

abner-chenc commented May 20, 2024

The SlowBots builder on linux-long64 is offline and I am currently unable to perform testing. However, I have checked the browser console and received the following error message:

buildbucket.js:862 Failed to schedule builds: Error: "user:abner.chenc@gmail.com" does not have permission "buildbucket.builds.add" in bucket "golang/try"
    at buildbucket.js:862:34
    at Array.forEach (<anonymous>)
    at module$exports$google3$third_party$java_src$gerritcodereview$plugins$buildbucket$web$cr$2dtryjob$2dpicker.CrTryjobPicker.scheduleSelectedBuilders (buildbucket.js:862:5)
    at async module$exports$google3$third_party$java_src$gerritcodereview$plugins$buildbucket$web$cr$2dtryjob$2dpicker.CrTryjobPicker.onAddTap (buildbucket.js:862:284)
(匿名) @ buildbucket.js:862
Promise.catch(异步)
handleAddTap @ buildbucket.js:862
handleEvent @ buildbucket.js:741

My gerrit account started using abner.chenc@gmail.com registered, later added chenguoqi@loongson.cn and has been using it all along chenguoqi@loongson.cn This email.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DevExp anything around developer experience NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Development

No branches or pull requests

2 participants