Go version
N/A — this is a builder infrastructure issue.
Output of go env in your module/workspace:
N/A — the task fails during LUCI scheduling, before the Go build starts.
What did you do?
OSU is decommissioning its POWER8 hardware, and the existing ppc64le builder VM
now runs on POWER9-backed infrastructure.
I inspected the LUCI task dimensions and the dimensions advertised by the
running bot.
The task requests:
cpu: ppc64le-64-POWER8
pool: luci.golang.shared-workers
The bot advertises:
cpu: ppc64le-64-POWER9
pool: luci.golang.shared-workers
What did you see happen?
The task remains pending and eventually expires without executing any build
steps.
Swarming reports:
0 bots could possibly run this task
What did you expect to see?
The builder should run on the oldest available Power architecture while
continuing to use the default GOPPC64 target.
This likely requires updating the server-side LUCI configuration to schedule
the builder on the available POWER9 bots.
Go version
N/A — this is a builder infrastructure issue.
Output of
go envin your module/workspace:What did you do?
OSU is decommissioning its POWER8 hardware, and the existing ppc64le builder VM
now runs on POWER9-backed infrastructure.
I inspected the LUCI task dimensions and the dimensions advertised by the
running bot.
The task requests:
The bot advertises:
What did you see happen?
The task remains pending and eventually expires without executing any build
steps.
Swarming reports:
0 bots could possibly run this taskWhat did you expect to see?
The builder should run on the oldest available Power architecture while
continuing to use the default
GOPPC64target.This likely requires updating the server-side LUCI configuration to schedule
the builder on the available POWER9 bots.