Add README for vibench_agent - #2906
Merged
Merged
Conversation
`ng_test_all` filters testable components to directories containing a README.md, then asserts the filtered count matches the discovered count. vibench_agent shipped without one in NVIDIA-NeMo#2674, so discovery found 174 components and tested 173, failing that assertion in all eight server-suite shards even though the selected module tests passed: AssertionError: Mismatch on the number of total modules found (174) and the number of actual modules tested (173)! Extra candidate paths: - responses_api_agents/vibench_agent Documents the build/harvest flow, why the agent owns its sandbox rather than sharing one, the bridged-network constraint that makes the stock docker config export an empty app, and the 0.0.0.0 exposure caveat. Setup and grading stay in the resources server README. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: raghavendran ramakrishnan <raramakrishn@nvidia.com>
cmunley1
approved these changes
Sep 1, 2026
Contributor
|
/ok to test 392047f |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
vibench_agentshipped without aREADME.mdin #2674.ng_test_allfilters testable components to directories containing one, then asserts the filtered count matches the discovered count — so discovery found 174 components and tested 173, failing that assertion in all eight server-suite shards even though every selected module test passed:nemo_gym/cli/env.py:1114, onmainat a2c5222.This adds the missing README. Docs-only — no code or config changes.
Contents
opencode_sandboxed_agent(only sandbox acquisition and harvesting are overridden).serialize()/connect(), which only OpenSandbox implements, so theswebenchshape cannot run on Docker, Apptainer or enroot. See Sandbox server to share sandbox states needed for rollouts #2082.configs/docker.yamlmust be used instead of the stock provider config — the stock 180s exec timeout kills long installs, and the harness is told the model is athttp://127.0.0.1:<port>, which inside a bridged container is the container itself, so it makes zero LLM calls and exports an empty app.network: host, and the0.0.0.0exposure caveat for the policy-model bind.Setup, task-row generation, reward definition and grading are not duplicated here; they stay in the resources server README.
Note on the other CI failure
The
Test Wheel Usefailure in that run is independent of this change: the wheel test enables prereleases/unsafe-best-match, unboundedmlflow>=3.15.1resolved to 3.15.2, which selectedsqlalchemy 2.1.0rc1, whose source metadata uv rejects (duplicate normalized extra name 'mssql-pymssql'), abortingarc_agi_resources_serverstartup. That needs a SQLAlchemy pin below 2.1 or prerelease containment in transitive resolution — happy to open a separate issue or PR for it if useful.🤖 Generated with Claude Code