Repository navigation
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 with no reviewable changes (1)
📝 WalkthroughWalkthroughThree nightly E2E jobs ( ChangesCloud Endpoints Inference Migration
Sequence Diagram(s)sequenceDiagram
participant Test as E2E Test
participant Helper as runHelperRoute
participant Script as ci-compatible-inference.sh
Test->>Helper: Execute with route & env options
Helper->>Script: Spawn bash with NVIDIA_INFERENCE_API_KEY
Script->>Script: Resolve provider route & endpoint
Script-->>Helper: Print routing state (base URL, provider, model)
Helper-->>Test: Return subprocess result
Test->>Test: Assert base=https://integrate.api.nvidia.com/v1
Test->>Test: Assert curl hits integrate.api not inference-api
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Code Coverage OverviewLanguages: TypeScript TypeScript / code-coverage/pluginThe overall coverage in the Show a code coverage summary of the most covered files.
TypeScript / code-coverage/cliThe overall coverage in the Show a code coverage summary of the most covered files.
Updated |
E2E Advisor RecommendationRequired E2E: None Full advisor summaryE2E Recommendation AdvisorBase: Required E2E
Optional E2E
New E2E recommendations
|
Vitest E2E Scenario RecommendationRequired Vitest E2E scenarios: None Full Vitest E2E advisor summaryVitest E2E Scenario AdvisorBase: Required Vitest E2E scenarios
Optional Vitest E2E scenarios
Relevant changed files
|
PR Review Advisor — InformationalMerge posture: Informational / low confidence This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision. |
Selective E2E Results — ❌ Some jobs failedRun: 28061797227
|
Selective E2E Results — ❌ Some jobs failedRun: 28063845807
|
Selective E2E Results — ❌ Some jobs failedRun: 28064080504
|
|
Closing this as a no-op. The final head restores the main hosted-compatible route and has no diff, while the original route-change direction was incorrect (it moved these jobs to public Build/integrate.api). We'll open a fresh focused PR for hermeticizing onboard-resume-e2e instead. |
Summary
onboard-resume-e2e,onboard-repair-e2e, andopenclaw-tui-chat-correlation-e2ethrough the NVIDIA Endpoints/Build provider path instead of the hosted OpenAI-compatible CI endpoint.secrets.NVIDIA_API_KEYasNVIDIA_INFERENCE_API_KEY,NEMOCLAW_PROVIDER=cloud, andnvidia/nemotron-3-super-120b-a12bfor those timeout-sensitive direct workflow lanes.Context
These three jobs timed out during hosted inference validation against
https://inference-api.nvidia.com/v1withcurl exit 28. This is the low-risk first slice of moving timeout-sensitive direct workflow jobs to the existing NVIDIA Endpoints path (https://integrate.api.nvidia.com/v1).Validation
git diff --checknpx biome check --write test/e2e-script-workflow.test.ts test/e2e-scenario/support-tests/hosted-inference.test.tsnpm test -- test/e2e-script-workflow.test.ts test/e2e-scenario/support-tests/hosted-inference.test.tsNotes
nemoclaw/node_modules/json5, missingnemoclaw/dist/blueprint/private-networks.js, and one local timeout), unrelated to these workflow-only changes.--no-verifyafter the targeted validation above.Summary by CodeRabbit
nvidia/nemotron-3-super-120b-a12b, removing hosted-inference wiring in affected scenarios.NVIDIA_INFERENCE_API_KEY.