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.

Sign up for GitHub

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

Jump to bottom

x/build: add LUCI linux-riscv64 builder #63481

Closed
mengzhuo opened this issue Oct 10, 2023 · 11 comments
Closed

x/build: add LUCI linux-riscv64 builder #63481

mengzhuo opened this issue Oct 10, 2023 · 11 comments
Assignees
@mengzhuo
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge new-builder
Milestone
Unreleased

Comments

@mengzhuo
Copy link
Contributor

mengzhuo commented Oct 10, 2023 •
edited
Loading

Following the instructions at Dashboard builders:

hostname linux-riscv64-mengzhuo

CSR is linux-riscv64-mengzhuo.csr.txt since Github doesn't seem to allow attaching with the name linux-riscv64-mengzhuo.csr origin issue asked for.
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label Oct 10, 2023
@gopherbot gopherbot added this to the Unreleased milestone Oct 10, 2023
@dmitshur dmitshur self-assigned this Oct 10, 2023
@dmitshur dmitshur moved this to In Progress in Go Release Oct 10, 2023
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/534976 mentions this issue: main.star: add openbsd-ppc64, linux-riscv64, freebsd-riscv64 builders

@dmitshur
Copy link
Contributor

dmitshur commented Oct 12, 2023 •
edited
Loading

Thanks. Here's the resulting certificate: linux-riscv64-mengzhuo-1697128389.cert.txt.

I've mailed CLs to define your new builder in LUCI and will comment once that's done.

gopherbot pushed a commit to golang/build that referenced this issue Oct 12, 2023
@dmitshur @gopherbot
main.star: add openbsd-ppc64, linux-riscv64, freebsd-riscv64 builders
38ee7a5 
Since the list of BUILDER_TYPES is nearly sorted, keep that up,
and sort (using 'Sort Lines' in $EDITOR) two of Linux run mods.

For golang/go#63480.
For golang/go#63481.
For golang/go#63482.

Change-Id: Icef633ab7a0d53b5807c2ab4a076d74c291dc0ea
Reviewed-on: https://go-review.googlesource.com/c/build/+/534976
TryBot-Bypass: Dmitri Shuralyov <[email protected]>
Reviewed-by: Carlos Amedee <[email protected]>
Auto-Submit: Dmitri Shuralyov <[email protected]>
Reviewed-by: Dmitri Shuralyov <[email protected]>
Reviewed-by: Heschi Kreinick <[email protected]>
@dmitshur
Copy link
Contributor

Step 3 is complete (CL 534976 is submitted), so you should be able to proceed with the next steps. Please feel free to comment here if you see something unexpected, or run into a problem that the documentation doesn't cover. Thanks.

@dmitshur dmitshur assigned mengzhuo and unassigned dmitshur Oct 12, 2023
@mengzhuo
Copy link
Contributor Author

@dmitshur I've setup the builder, however I don't know how to debug with log https://chromium-swarm.appspot.com/task?id=655ba20db7351610

Any tips?

@dmitshur
Copy link
Contributor

dmitshur commented Oct 20, 2023 •
edited
Loading

BOT_DIED sounds like the bot running on your builder crashed, although it did run for 4m 13s. Is there anything useful in logs on your side? I'm not spotting much on the LUCI end so far.

CC @cagedmantis if you have a chance to look this week.

@cagedmantis
Copy link
Contributor

@mengzhuo I think the logs on https://chromium-swarm.appspot.com/bot?e=true&id=linux-riscv64-mengzhuo might be helpful. Try selecting the events tab.

@cagedmantis
Copy link
Contributor

cc @golang/release

@dmitshur
Copy link
Contributor

It looks like the builder has passed some times by now, e.g., there are recent "SUCCESS" entries at https://ci.chromium.org/ui/p/golang/builders/ci/gotip-linux-riscv64 and https://ci.chromium.org/ui/p/golang/builders/ci/x_tools-gotip-linux-riscv64. The "INFRA FAILURE" entries appear to be due to resource exhaustion, that is the (expected) limited availability of the machine.

@mengzhuo Is there more to do here before considering the builder as added? If the INFRA FAILURES is all that's left, perhaps we can start a new tracking issue for that specifically. It's also fine to keep using this one, I just wanted to update its status.

@mengzhuo
Copy link
Contributor Author

@dmitshur sure, thanks.

@github-project-automation github-project-automation bot moved this from In Progress to Done in Go Release Nov 29, 2023
@dmitshur
Copy link
Contributor

dmitshur commented Dec 5, 2023

@mengzhuo If your builder continues to be in "Quarantined—Had 2 consecutive BOT_DIED tasks" state for a prolonged amount of time (I see that status here at this moment), can you try rebooting the swarming bot and seeing if that helps? CL 546715 might help, but if this continues to be a problem let's open a new issue for it. Thanks.

@dmitshur dmitshur mentioned this issue Dec 5, 2023
Open
13 tasks
@mengzhuo
Copy link
Contributor Author

mengzhuo commented Dec 6, 2023

@dmitshur I had restart it. I think some of failures might cause by flaky network.

@golang golang locked and limited conversation to collaborators Dec 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mengzhuo mengzhuo

Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge new-builder
Projects
Go Release
Archived in project
Milestone
Unreleased
Development

No branches or pull requests
4 participants
@cagedmantis @mengzhuo @dmitshur @gopherbot