gmanal - test change#9277
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughSummary by CodeRabbit
Walkthroughsuggestion: New GitHub Actions workflow "nvcr image pull + size" triggers on ChangesNVCR Image Pull Smoke Test
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
.github/workflows/test-nvcr-pull.yml (1)
47-53: ⚡ Quick winsuggestion: Add
timeout-minuteson the job to cap hangs in network/docker steps; without it, a stuck run can consume self-hosted capacity for hours and increase CI fanout cost.As per coding guidelines, for
.github/**/*reviews should focus on “avoiding unnecessary CI fanout”.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 4f5ca60d-9f7c-4bad-8228-f93e2aedd998
📒 Files selected for processing (1)
.github/workflows/test-nvcr-pull.yml
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
.github/workflows/test-nvcr-pull.yml (1)
31-31:⚠️ Potential issue | 🟠 Major | ⚡ Quick winimportant: Add
timeout-minuteson thepull-and-sizejob to cap stuck pulls/registry hangs on self-hosted runners. Missing timeout can tie up runner capacity and delay required checks.
🧹 Nitpick comments (1)
.github/workflows/test-nvcr-pull.yml (1)
52-54: ⚡ Quick winsuggestion: Don’t fully suppress cleanup failures on Line 54.
|| truehides persistent cleanup problems on self-hosted runners; at minimum, emit a warning when removal fails so disk-growth issues are visible in logs.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: e968a478-50ea-4eb0-ab90-f2cd9b3e327e
📒 Files selected for processing (1)
.github/workflows/test-nvcr-pull.yml
| # on contributor forks where nv-gha-runners labels do not resolve. | ||
| runs-on: ${{ github.repository == 'NVIDIA/cccl' && 'linux-amd64-cpu4' || 'ubuntu-latest' }} | ||
| env: | ||
| NVCR_IMAGE: nvcr.io/nvidian/prodsec/pulse-trufflehog:1.33 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
FILE=".github/workflows/test-nvcr-pull.yml"
echo "=== file ==="
ls -l "$FILE"
echo
echo "=== snippet around line 37 ==="
nl -ba "$FILE" | sed -n '1,120p'Repository: NVIDIA/cccl
Length of output: 247
🏁 Script executed:
#!/bin/bash
set -euo pipefail
FILE=".github/workflows/test-nvcr-pull.yml"
echo "=== file ==="
ls -l "$FILE"
echo
echo "=== lines 1-120 with numbers (no nl) ==="
cat -n "$FILE" | sed -n '1,120p'
echo
echo "=== lines around NVCR_IMAGE ==="
rg -n "NVCR_IMAGE" "$FILE" || true
echo
echo "=== lines around job steps cleanup/docker rmi ==="
rg -n "docker rmi|cleanup" "$FILE" || true
echo
echo "=== search for timeout-minutes ==="
rg -n "timeout-minutes" "$FILE" || trueRepository: NVIDIA/cccl
Length of output: 2871
important: Pin NVCR_IMAGE to an immutable digest instead of the mutable :1.33 tag to keep the workflow reproducible and strengthen supply-chain trust (line 37).
- suggestion: Add
timeout-minutestojobs.pull-and-sizeand avoid masking cleanup failures (docker rmi ... || true) so self-hosted runner hygiene issues don’t get hidden (lines 31-37, 52-54).
😬 CI Workflow Results🟥 Finished in 1h 28m: Pass: 99%/501 | Total: 3d 07h | Max: 57m 11s | Hits: 99%/625845See results here. |
Description
closes
Checklist