x/build/dashboard: update dragonfly to 6.4.0 #64684
Labels
Builders
x/build issues (builders, bots, dashboards)
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
new-builder
OS-Dragonfly
Milestone
Comments
dmitshur
added
NeedsInvestigation
|
It seems the work of adding these builders to LUCI hasn't been done yet (#61092), so it might make sense to use 6.4.0 instead of 6.2.2 when doing that. (Since we're actively moving towards LUCI, there's less value in trying to do this update in the old infra at this point.) @tuxillo, are you able to take a look at what adding this to LUCI would take? Also see #63471 and #60468. CC @prattmic if you have a chance to look. |
|
Change https://go.dev/cl/549035 mentions this issue: |
35 tasks
gopherbot
pushed a commit
to golang/build
that referenced
this issue
Dec 14, 2023
Initial work to move from dfly 6.2.2 to 6.4.0. For golang/go#64684. Change-Id: I67e951ccb34728d9b42980cdd3cf1c9739fbc395 GitHub-Last-Rev: e672ce4 GitHub-Pull-Request: #83 Reviewed-on: https://go-review.googlesource.com/c/build/+/549035 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Michael Pratt <mpratt@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
|
has there been any progress? not sure what to do next. |
|
This will probably need to look something like https://go.dev/cl/526618, as that is another port that runs on GCE. We will also need to do some internal work to get LUCI to launch these VMs. I can take a look at making adjustments to the image. Unfortunately, I tried to create the existing image, which failed in phase 2 trying to download packages: Do you know what may be the problem here? |
Yeah, let me come up with a set of commands that can be actually put into a script. It's a problem with 6.4.0 alone that will be fixed in later releases (and it is fixed in latest). |
|
Ah, thanks for the quick response. I'll try 6.2.2 for now. |
|
6.2.2 gets further, but it is unfortunately broken as well: |
For 6.4.0, can you please try the following? Make sure after the failure, you do the command below and then retry the Context: There was a bug that was triggered in the pkg 1.14 upgrade which ended up deleting the repos configuration. |
|
That did not work either, the second run failed with: You could be able to run the image creation process as well, by running |
To this original question, the best baseline for LUCI migration is the port of the openbsd-amd64 builder image in CL 526618, plus minor follow-ups in CL 528515 and CL 542064. The key parts are:
You won't be able to fully test this until it is running on GCE with swarming access, but it should be testable that at least bootstrapswarm attempts to access the swarming server and gets an authentication error. |
Let me try myself and come back to you with something that actually works. Sorry for the hassle! |
This comment was marked as resolved.
This comment was marked as resolved.
|
@prattmic created a PR for the 6.4.0 build issue. I have tested it in Debian. |
|
Change https://go.dev/cl/568315 mentions this issue: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's long due but we should update the gobuilder from dfly 6.2.2 to 6.4.0
The text was updated successfully, but these errors were encountered: