nemo-rl-e2e-testing

Tests WebRTC-based real-time audio/video communication in automated workflows.

Updated May 23, 2026
One-click install
npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemo-rl-e2e-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemo-rl-e2e-testing
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/Megatron-Bridge/nemo-rl-e2e-testing
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemo-rl-e2e-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams confidently validate that a Megatron-Bridge model/provider change works end-to-end when driven by NeMo-RL’s external RL training loop, catching integration failures that Bridge-only tests can miss.

Core Features & Use Cases

  • Downstream NeMo-RL compatibility validation: Runs NeMo-RL Megatron policy GRPO/SFT jobs from the current Bridge checkout to verify rollout, reward/logprob wiring, and policy setup end-to-end.
  • Coverage levels for real change types: Supports increasing validation depth from a Level 0 short GRPO smoke to LoRA/checkpoint variants, non-colocated vLLM refits, optional Megatron generation backend paths, parallelism stress, architecture-specific runs, and learning-signal checks.
  • Evidence-focused reporting: Produces metrics outputs (including metrics.json), records how NeMo-RL resolves the Bridge checkout (via import path), and enables pass/fail assessment with explicit pass criteria.

Quick Start

Run a Level 0 NeMo-RL external-loop GRPO Megatron smoke using the maintained wrapper command: uv run bash tests/functional/grpo_megatron.sh

Frequently Asked Questions about nemo-rl-e2e-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Megatron-Bridge changes for NeMo-RL compatibility?

You can validate Megatron-Bridge changes by running NeMo-RL end-to-end external RL loop tests that exercise Megatron policy setup, HF import/export, checkpointing, and weight transfer into generation backends.

How does end-to-end testing verify HF import/export and vLLM refits in NeMo-RL?

End-to-end testing verifies HF import/export via Bridge and non-colocated vLLM refits by running GRPO/SFT jobs that exercise rollout, reward/logprob wiring, and policy setup to catch integration failures.

How do I run a GRPO Megatron smoke test for NeMo-RL?

Run a Level 0 NeMo-RL external-loop GRPO Megatron smoke test using the maintained wrapper command: uv run bash tests/functional/grpo_megatron.sh.

Can I test checkpoint resume and LoRA variants with NeMo-RL Megatron policies?

Yes, you can test checkpoint resume and LoRA variants by selecting higher coverage levels that validate non-vanilla Bridge provider paths, parallelism stress, and architecture-specific model families.

Do I need a local Bridge checkout to run NeMo-RL end-to-end tests?

Yes, you need a local Bridge checkout integrated via PYTHONPATH, and an explicit NeMo-RL check ensures the intended Bridge import path is used during the test run.

What evidence does NeMo-RL end-to-end testing collect for pass/fail assessment?

NeMo-RL end-to-end testing collects evidence-focused reporting through metrics.json outputs, records Bridge checkout resolution paths, and enables explicit pass criteria assertions for evaluation.