Repository navigation
ci(nightly): preserve artifact handoffs while fixing skipped validation - #250
Conversation
Signed-off-by: Jason Zhou (Engrg-Hardware 1) <jasonzho@nvidia.com>
Signed-off-by: Jason Zhou (Engrg-Hardware 1) <jasonzho@nvidia.com>
Remove the nightly-dist uploads — Artifactory is the only channel. FPE builds its own qualification wheel at the same SHA, and e2e accuracy always builds from source. Also override the implicit success() on license-evidence and fpe-support-matrix so the approval job skipped on scheduled runs cannot cascade and skip the GitLab trigger.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: 📒 Files selected for processing (2)
🔗 Linked repositories identifiedCodeRabbit considers these linked repositories for cross-repo context during reviews:
Included review availability: Your plan provides up to 12 included reviews per hour; 8 remain after this review. 📜 Recent review details🧰 Additional context used📓 Path-based instructions (4)Only root workflows are active.⚙️ CodeRabbit configuration file Files:
Require coverage of the changed behavior and its negative or boundary cases.⚙️ CodeRabbit configuration file Files:
Read REVIEW.md before commenting.⚙️ CodeRabbit configuration file Files:
Before making any change under: `python/aisimulate/src/aiconfigurator/generator/**` MUST read: `python/aisimulate/.claude/rules/generator-development.md` Before making any change under `python/aisimulate/collector/**` MUST read: `python/ais...📄 CodeRabbit inference engine (AGENTS.md) Files:
🪛 ast-grep (0.45.3)tests/test_ci_workflow_contracts.py[info] 1797-1797: use of eval can be insecure (no-eval-python) 🔀 Multi-repo context ai-dynamo/aiconfigurator, ai-dynamo/dynamoLinked repositories findingsai-dynamo/aiconfigurator
ai-dynamo/dynamo
📝 SummaryRisk: medium. Human attention should focus on cancellation predicates, dependency-result handling, and final Full CI status. Changed behavior
Technical quality
Merge readiness
WalkthroughNightly CI conditions now block selected jobs after cancellation or unsuccessful required dependencies. Contract tests simulate cancellation and validate dependency and build-selection outcomes. ChangesNightly CI guards
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The nightly jobs now remain blocked after cancelled, skipped, or failed prerequisites while successful scheduled builds can proceed. No current merge-blocking risk is identified. 🚥 Pre-merge checks | ✅ 8✅ Passed checks (8 passed)
Comment |
jasonqinzhou
left a comment
There was a problem hiding this comment.
Reviewed the current head against main 920453e. The explicit status predicates address the scheduled-run skip cascade. Two artifact-contract regressions need correction before this can merge. I am preparing the fixes on this PR as requested, retaining the nightly consumer handoff and limiting this change to the skip fix. Existing validation also reproduces one Python artifact-contract failure and three accuracy-workflow failures.
Signed-off-by: Jason Zhou (Engrg-Hardware 1) <jasonzho@nvidia.com>
jasonqinzhou
left a comment
There was a problem hiding this comment.
Fresh Codex review of 07a6b70 against main 920453e: no remaining actionable finding in the final two-file diff. Both artifact-contract regressions are fixed and their threads resolved. The verified wheel/provenance handoff is unchanged from main; explicit !cancelled() predicates preserve required dependency failures while allowing skipped approval ancestors. Local validation: 19 focused Python workflow contracts, 8 Node consumer tests, Ruff, and whitespace checks pass. Current Fast CI is green and CodeRabbit substantively reviewed both files at this exact head with no actionable comments. The broader strict-warning suite has three pre-existing license-evidence resource-warning failures; PR #241 fixes them. Full CI is still required before merge; this review does not waive that gate or the independent approval required on #241.
|
/ok to test 07a6b70 |
Signed-off-by: Jason Zhou (Engrg-Hardware 1) <jasonzho@nvidia.com>
Signed-off-by: Jason Zhou (Engrg-Hardware 1) <jasonzho@nvidia.com>
jasonqinzhou
left a comment
There was a problem hiding this comment.
Refreshed Codex review at b44fda2 after merging main c3cc310. The final two-file diff is unchanged from reviewed 07a6b70; no new actionable finding. The !cancelled() predicates require successful build/compliance inputs and retain the exact verified wheel/checksum/provenance handoffs. Integration with current #241 remains conflict-free. The old-head Full CI run was cancelled after the base advanced; it is not current evidence. Merge order remains #241 then #250 then #251: #241 fixes known strict application-contract failures inherited by the other branches. Current automated review, Full CI, and approval gates still apply.
jasonqinzhou
left a comment
There was a problem hiding this comment.
Technical approval of the final two-file change at b44fda2. The validated review findings are fixed, both threads are resolved, verified artifact handoffs are preserved, and the skip/cancellation/dependency regression tests pass. Current Fast CI is green. This approval does not authorize bypassing the remaining merge gates: land #241's existing contract-failure fixes, refresh this branch, and require completed current-head CodeRabbit and Full CI before merging.
Signed-off-by: Jason Zhou (Engrg-Hardware 1) <jasonzho@nvidia.com>
Signed-off-by: Jason Zhou (Engrg-Hardware 1) <jasonzho@nvidia.com>
jasonqinzhou
left a comment
There was a problem hiding this comment.
Fresh review and approval at 9bf86e2 against main 6c07147 after #241 landed. The final diff remains the two explicit nightly status predicates and their regression tests; no actionable finding remains. The verified wheel/checksum/provenance handoffs are preserved. All 222 workflow/qualification/release tests now pass under warnings-as-errors, including the three previously blocked by #241. The final main-merge commit is tree-identical to that tested local integration. Current-head CodeRabbit, Fast CI, and Full CI must pass before the squash merge.
|
/ok to test 9bf86e2 |
Scheduled nightlies skip the manual-approval ancestor, which can also suppress downstream validation through Actions' implicit success() condition. Give license-evidence and fpe-support-matrix explicit !cancelled() predicates with successful dependency requirements so they run after an unattended successful build and still reject cancellation or failed inputs.
The verified nightly-dist wheel, checksum, and provenance artifacts remain available to FPE, accuracy, and installation consumers. FPE continues to qualify the same wheel downloaded from Artifactory.
Validation at
9bf86e2743a22f1c6ddcfa0a8ad5873f7f0a5f0d, based on main6c07147aafter #241: 222 workflow/qualification/release tests pass under root pytest.ini warnings-as-errors. The focused accuracy consumer suite has 8 passing Node tests; Ruff, actionlint, and whitespace checks pass. Regression coverage includes skipped approval ancestors, cancellation, failed/skipped/cancelled dependencies, and unchanged-source suppression. Both review threads are fixed and resolved. CodeRabbit, Fast CI, and Full CI passed at this exact head. Squash-merged asdfa8a1fdac8374058b91d797e8a8bc433b05f406; the merged tree was verified identical to the tested head.