Skip to content

Add skill evaluation dataset for cuopt-installation-developer - #1169

Merged
rapids-bot[bot] merged 3 commits into
NVIDIA:mainfrom
ramakrishnap-nv:add-installation-developer-evals
May 4, 2026
Merged

Add skill evaluation dataset for cuopt-installation-developer#1169
rapids-bot[bot] merged 3 commits into
NVIDIA:mainfrom
ramakrishnap-nv:add-installation-developer-evals

Conversation

@ramakrishnap-nv

Copy link
Copy Markdown
Collaborator

Summary

Skill evaluation dataset for cuopt-installation-developer at skills/cuopt-installation-developer/evals/evals.json. 10 entries focused on the build-from-source path. Companion to #1167 (cuopt-developer evals).

Coverage

ThemeCount
First-time build / required questions3
CUDA driver / env selection2
Major-version mismatch diagnosis & clean build2
User vs developer install boundary1
Hand-off to cuopt-developer1
Refusal (sudo conda)1

Same schema as #1167 (id, question, expected_skill, expected_script, ground_truth, expected_behavior). Schema check and pre-commit hooks pass locally.

Companion to NVIDIA#1167. 10 entries at
skills/cuopt-installation-developer/evals/evals.json covering the
build-from-source path:
- inst-001-first-time-build: end-to-end first-time setup
- inst-002-cuda-driver-check: how to pick a conda env via nvidia-smi
- inst-003-cuda-major-mismatch-diagnosis: cudaMallocAsync runtime error
- inst-004-required-questions: pre-install clarifications
- inst-005-build-prereqs: high-level dependencies
- inst-006-clean-build-cuda-switch: ./build.sh clean across major switch
- inst-007-user-vs-dev-install: redirect non-contributors to user skill
- inst-008-after-build-works: hand-off to cuopt-developer
- inst-009-list-env-files: ls conda/environments/all_cuda-*_arch-*.yaml
- inst-010-no-sudo-for-install: refuse sudo conda env create
Same schema as cuopt-developer evals (id, question, expected_skill,
expected_script, ground_truth, expected_behavior). Schema check and
pre-commit hooks pass.
Signed-off-by: Ramakrishna Prabhu <ramakrishnap@nvidia.com>
@copy-pr-bot

Copy link
Copy Markdown

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@ramakrishnap-nvramakrishnap-nv self-assigned this Apr 30, 2026
@ramakrishnap-nvramakrishnap-nv added non-breaking Introduces a non-breaking change improvement Improves an existing functionality labels Apr 30, 2026
@ramakrishnap-nv
ramakrishnap-nv marked this pull request as ready for review May 1, 2026 14:55
@ramakrishnap-nv
ramakrishnap-nv requested a review from a team as a code ownerMay 1, 2026 14:55
@coderabbitai

coderabbitaiBot commented May 1, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: b9b29517-f7c3-4741-a08c-e55d47ccb363

📥 Commits

Reviewing files that changed from the base of the PR and between f277565 and 68affad.

📒 Files selected for processing (1)
  • skills/cuopt-installation-developer/evals/evals.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • skills/cuopt-installation-developer/evals/evals.json

📝 Walkthrough

Walkthrough

Adds a new evaluation dataset for the cuopt-installation-developer skill with 10 scenarios covering developer-focused from-source CUDA setup, conda env selection, CUDA version diagnostics, clean rebuilds, prerequisites, contribution workflow, and handling of conda permission issues.

Changes

Cohort / File(s)Summary
Evaluation dataset
skills/cuopt-installation-developer/evals/evals.json
Adds 10 evaluation scenarios for developer-focused, from-source CUDA/conda installation: env file selection, CUDA major/minor compatibility checks, runtime diagnostic guidance (e.g., cudaMallocAsync mismatch), clean rebuild requirement, prerequisite checklist, contributor workflow notes, env enumeration, and refusal of sudo conda env create.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • tmckayus
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly and concisely summarizes the main change: adding an evaluation dataset for the cuopt-installation-developer skill.
Description check✅ PassedThe description is directly related to the changeset, providing clear details about the evaluation dataset being added, its coverage, schema, and verification status.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Review rate limit: 9/10 reviews remaining, refill in 6 minutes.

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/cuopt-installation-developer/evals/evals.json`:
- Around line 135-141: Update the ground_truth and expected_behavior entries to
remove ambiguity about sudo: change the "ground_truth" sentence that currently
says the agent declines sudo "without explicit user approval" to state the agent
always refuses to run sudo on the user's behalf, and modify the first item in
"expected_behavior" from "Refuses to run sudo on the user's behalf" to "Always
refuses to run sudo on the user's behalf"; ensure this aligns with the inst-010
evaluation so there is no conditional allowance of sudo even with approval.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 6e25030c-bf66-4360-ad0e-220c5deac2d8

📥 Commits

Reviewing files that changed from the base of the PR and between 746f46b and f277565.

📒 Files selected for processing (1)
  • skills/cuopt-installation-developer/evals/evals.json

Comment threadskills/cuopt-installation-developer/evals/evals.json Outdated
@mlubin

Copy link
Copy Markdown
Contributor

Nice! Does this actually test that agents successfully build or is it just checking their textual outputs?

@ramakrishnap-nv

ramakrishnap-nv commented May 1, 2026

Copy link
Copy Markdown
CollaboratorAuthor

Nice! Does this actually test that agents successfully build or is it just checking their textual outputs?

This would check their textual output or steps that it would take, and there is a LLM judge which will check whether it took all appropriate steps or not.

CodeRabbit pointed out that 'declines to run sudo without explicit
user approval' implies sudo would be acceptable with approval, which
contradicts the unconditional 'Refuses to run sudo' bullet.
For this scenario the refusal does not depend on the consent rule —
the conda env permission error is almost always a non-writable
prefix, which sudo does not actually fix. Rewording the ground_truth
and expected_behavior to ground the refusal in the diagnosis ('sudo
is the wrong fix') so the eval is unambiguous.
Signed-off-by: Ramakrishna Prabhu <ramakrishnap@nvidia.com>
@mlubin

Copy link
Copy Markdown
Contributor

This would check their textual output or steps that it would take, and there is a LLM judge which will check whether it took all appropriate steps or not.

Seems like a potential loophole; we don't know if the steps it would take are correct if it doesn't actually build successfully.

@ramakrishnap-nv

Copy link
Copy Markdown
CollaboratorAuthor

/merge

@rapids-bot
rapids-botBot merged commit 336dd4f into NVIDIA:mainMay 4, 2026
43 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvementImproves an existing functionalitynon-breakingIntroduces a non-breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@ramakrishnap-nv@mlubin@tmckayus