Skip to content

x/build/cmd/racebuild: Error running create: failed to create buildlet on gotip-linux-loong64 #73287

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 Apr 9, 2025 · 3 comments
Labels
Builders x/build issues (builders, bots, dashboards) NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@abner-chenc
Copy link
Contributor

abner-chenc commented Apr 9, 2025

Hi,

Currently, the support for linux/loong64 by the tsan library in llvm has been landed , and the racebuild command already has support for linux/loong64. However, when I build race_linux_loong64.syso for this CL through the racebuild command, the following error occurs:

[golang@linux-loong64--01 ~]$ racebuild -platforms linux/loong64 -rev c9280ba25aef6cd47e973a439da23c7b52bddb56 -goroot /home/golang/src/go
2025/04/09 18:58:04 using Go revision: af278bfb1f07b9f8f84d325a84b3891a3ab0dbf1
2025/04/09 18:58:04 linux/loong64: gomote [create -status=false gotip-linux-loong64]
Please visit https://www.google.com/device in your browser and enter verification code:
 JPQ-RVJ-KWX
# Error running create: failed to create buildlet (1): rpc error: code = PermissionDenied desc = unexpected HTTP status code received from server: 403 (Forbidden); transport: received unexpected content-type "text/html; charset=UTF-8"
2025/04/09 18:58:26 linux/loong64: gomote [create -status=false gotip-linux-loong64] failed:
Please visit https://www.google.com/device in your browser and enter verification code:
 JPQ-RVJ-KWX
# Error running create: failed to create buildlet (1): rpc error: code = PermissionDenied desc = unexpected HTTP status code received from server: 403 (Forbidden); transport: received unexpected content-type "text/html; charset=UTF-8"
2025/04/09 18:58:26 linux/loong64: instance creation failed, retrying
2025/04/09 18:58:26 linux/loong64: gomote [create -status=false gotip-linux-loong64]
# Error running create: failed to create buildlet (1): rpc error: code = PermissionDenied desc = unexpected HTTP status code received from server: 403 (Forbidden); transport: received unexpected content-type "text/html; charset=UTF-8"
2025/04/09 18:58:27 linux/loong64: gomote [create -status=false gotip-linux-loong64] failed:
# Error running create: failed to create buildlet (1): rpc error: code = PermissionDenied desc = unexpected HTTP status code received from server: 403 (Forbidden); transport: received unexpected content-type "text/html; charset=UTF-8"
2025/04/09 18:58:27 linux/loong64: instance creation failed, retrying

gerrit account: [email protected]
google account: [[email protected]]
github account: abner-chenc

@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label Apr 9, 2025
@gopherbot gopherbot added this to the Unreleased milestone Apr 9, 2025
@dmitshur dmitshur added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Apr 10, 2025
@dmitshur
Copy link
Member

Does gomote creation work standalone from racebuild, or does it run into the same error? When authenticating, which of the two emails are you using, the @gmail.com one?

Right now gomote access is granted to your primary Gerrit email (the @loongson.cn one). I've replaced it with your @gmail.com one, can you try again?

CC @golang/release.

@abner-chenc
Copy link
Contributor Author

abner-chenc commented Apr 11, 2025

Thanks, now I can trigger the racebuild build. I think it might be similar to #67468.

@dmitshur
Copy link
Member

Yes, there is some similarity to #67468, but it's not the same issue. Over there it is a problem on the side of Gerrit, where for some reason triggering optional trybots doesn't use your primary Gerrit email for auth.

In the case of gomotes, we're using a different system for auth, and so it just needs to match the email you use when you authenticate to it.

@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Apr 11, 2025
@dmitshur dmitshur moved this to Done in Go Release Apr 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Builders x/build issues (builders, bots, dashboards) NeedsFix The path to resolution is known, but the work has not been done.
Projects
Archived in project
Development

No branches or pull requests

3 participants