Nemo Gym Debugging

Invocation Check

Use this skill when something failed or looks suspicious in a Nemo Gym run. If the task is adding a new env, use the add-benchmark skill; if it is changing profiling behavior, use the nemo-gym-reward-profiling skill.

Debug by classification, not by guessing. The first goal is to decide whether the issue is:

• infra: Slurm, Ray, container, filesystem, network, ports
• model serving: vLLM startup/readiness/throughput
• config: wrong config bundle, missing agent, wrong extra args
• data/schema: JSONL fields do not match verifier/resource server expectations
• verifier/runtime: resource server exception or malformed verify response
• cache/resume: stale materialized inputs or partial rollout output
• throughput/resources: concurrency too high, judge bottleneck, tool/sandbox latency

Debug Order