scverse / scverse/gpu-ci-config
latest AMI `ami-0285bfb786db80af3` in Actions does not have `nvidia-smi`
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
So I am really new to this, please forgive any mistakes.
I checked the https://github.com/scverse/gpu-ci-config/actions/workflows/build-ami.yml section and found the latest image as ami-0285bfb786db80af3 which I then plugged into https://github.com/scverse/anndata/pull/2269 but nvidia-smi didn't work.
I also tried running the "Update AMI" CI job as per the README.md and that errored out with a 403 on making the PR: https://github.com/scverse/gpu-ci-config/actions/runs/20598977237/job/59159801996 but I don't expect there to be any difference in the outcome (broken nvidia-smi).
As a final check, I tested the image using https://github.com/scverse/gpu-ci-config/actions/runs/20599052838/job/59160046962
I must be missing some step of the process. What's up here?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with build-ami.yml and README.md to understand how the AMI is built, selected, and updated. Inspect the linked Update AMI job and image-test run, focusing on the 403 and the missing nvidia-smi behavior. Done means the generated AMI supports nvidia-smi and the documented update workflow completes without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github-actions, shell
- Domain
- ci-cd, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100