ci: macOS contributor nightly fails to build aws-lc-fips-sys (Could not find Go)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- build-system, ci-cd
Research direction
Look at the failing workflow file .github/workflows/macos-contributor.yml. Compare it to other workflows like release-linux-node-clients to see how they install Go (e.g., using actions/setup-go). Add a similar step before the cargo build, pinning the same Go version (1.24.4). Test by triggering a workflow dispatch or waiting for the next scheduled run to verify the fix.
Written by the indexing model from the issue text.
Description
macos-contributor.yml has failed on both scheduled runs so far (2026-09-23 run 35806689667, 2026-09-24 run 35943074185).
The job "Direct Cargo binaries and database-free gates" stops while compiling aws-lc-fips-sys v0.14.2 on aarch64-apple-darwin:
CMake Error at aws-lc/cmake/go.cmake:6 (message):
Could not find Go
The FIPS build of AWS-LC needs Go at build time. The Linux jobs install it explicitly (for example release-linux-node-clients pins Go 1.24.4, and render-golden uses go-1.24.4 in its cache key), but the macOS runner image does not provide Go on PATH for this workflow.
Expected fix: add a pinned actions/setup-go step (same version as the other workflows) before the first cargo build in macos-contributor.yml, then confirm one scheduled or dispatched run is green.
Found during the 2026-09-24 CI speed review.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- Avg merge
- 4h 26m
- Merged PRs (30d)
- 152
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from registrystack/registry-stack
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1383 ·
-
area:breg enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
registrystack/registry-stack#1380 ·
-
area:breg enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1379 ·
-
area:casework documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
registrystack/registry-stack#1369 ·
-
area:casework bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1368 ·
All issues in registrystack/registry-stack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
longbridge/gpui-kit#3223 ·
-
bug engine
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rocky-data/rocky#2181 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
oasisprotocol/oasis-sdk#2523 ·
-
[indexer] [QA] Add a focused test for the new NonRetryableError / assertSocketAlive() behavior. Openbot:ai-assisted component:indexer QA-roadmap status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
midnightntwrk/midnight-indexer#1557 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Luminous-Dynamics/mycelix#3069 ·