-
Notifications
You must be signed in to change notification settings - Fork 17.6k
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
x/build: add LUCI aix-ppc64 builder #67299
Comments
We are working on getting a AIX machine in OSU lab for this purpose. |
CC @golang/aix. |
I'll try poking around with this since I came into access to the VM. I've chosen the hostname as (edit: fix hostname to match prevailing conventions, edit 2: revert to original naming) |
Change https://go.dev/cl/600995 mentions this issue: |
@pmur I see you've edited that post, replacing Are you okay to go back to |
Oops. I'd prefer to stick with |
Thanks. Here's the certificate: aix-ppc64-power8-1721862086.cert.txt. Also noting that if the previous coordinator-based builder starts to get in the way of you bringing up the new LUCI builder, you should feel free to stop the previous builder and focus on the new one. It's certainly fine to keep the old one running if it doesn't get in the way. Thanks. |
For golang/go#67299. Change-Id: I76f511338617f6b431c396f048200d25e09dd275 Reviewed-on: https://go-review.googlesource.com/c/build/+/600995 Reviewed-by: Dmitri Shuralyov <[email protected]> Auto-Submit: Dmitri Shuralyov <[email protected]> Reviewed-by: Cherry Mui <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]>
I am still in the process of getting LUCI working. I had to update the OSS software, and that has been rather bumpy. I have the swarming client running, though I suspect I will need to solve more issues once the backend pieces are updated. This has led to some (hopefully) intermittent failures of the old builder. |
The LUCI aix bot is up, though I think something needs to be updated on the backend. It has not run any jobs yet. The cpu and cipd_platform values look suspect. |
Indeed. The CIPD binaries built for GOOS=aix GOARCH=ppc64 are using "aix-ppc64" (https://chrome-infra-packages.appspot.com/p/infra/experimental/golangbuild/aix-ppc64), so it's intended for the bot to report its cipd_platform dimension as that (instead of the current "aix-00fac25f4b00"). That dimension is also used for match the bot to the builder definitions (e.g., gotip-aix-ppc64). There are zero matches at https://chromium-swarm.appspot.com/botlist?f=cipd_platform%3Aaix-ppc64&f=pool%3Aluci.golang.shared-workers now—hence the bot isn't getting any jobs. |
The aforementioned issue is fixed in crrev.com/c/5775509, thanks. A build for gotip-aix-ppc64 builder was now able to start at https://ci.chromium.org/b/8739762966790400417, failing with "CIPD error: invalid_version_error with package infra/tools/luci/cas/aix-ppc64, version git_revision:2aba496613f92a5b06d577f82b5d028225d3d577 on path None". While we do have a aix-ppc64 binary for golangbuild (https://chrome-infra-packages.appspot.com/p/infra/experimental/golangbuild), there isn't one for some other dependencies like |
Other binaries like bb, rdb, result_adapter, and so on are already there. The reason we didn't end up with a
The problem in that particular dependency appears to be reported in dgraph-io/badger#2035, and the x/sys/unix issue #64669 is related. |
@dmitshur are there any other dependencies which do not compile for aix? I have an attempt to get badger (v4) running on aix, but I need to get approval to post and contribute the patch. I am not sure how long that will take. |
Thanks for working on this Paul. From what I can tell this case ( Here's a quick check I did just now. Looking at a recent build for another fairly similar port openbsd/ppc64 at https://chromium-swarm.appspot.com/task?id=6bd610f803408d10, there seem to be mentions 14 CIPD packages. Out of those, cas is the only one not resolved for aix-ppc64 platform:
|
There currently isn't a LUCI builder that tests the aix/ppc64 port (other than the misc-compile builder, which tests only that the port compiles). This is the tracking issue for it.
The next steps that a builder owner will need to follow to make progress here are documented https://go.dev/wiki/DashboardBuilders#luci-builders.
The text was updated successfully, but these errors were encountered: