Skip to content

test(verifiers): cover default rollout path - #2695

Draft
santho090 wants to merge 1 commit into
radixark:mainfrom
santho090:codex/issue-2560-verifiers-default-e2e
Draft

test(verifiers): cover default rollout path#2695
santho090 wants to merge 1 commit into
radixark:mainfrom
santho090:codex/issue-2560-verifiers-default-e2e

Conversation

@santho090

@santho090 santho090 commented Aug 21, 2026

Copy link
Copy Markdown

What

Run the existing Verifiers training E2E through verifiers_rollout.VerifiersRolloutFn, the shipped default, and stop forcing the legacy rollout path.

Why

The sole Verifiers training E2E still selects verifiers_rollout.generate_rollout and sets MILES_USE_LEGACY_ROLLOUT_V1=1. Unit tests check how the launcher selects a rollout function, but they do not run the default adapter through Verifiers, SGLang, and the Miles training loop.

This patch keeps the existing sample, log-probability, trainability, and reward assertions unchanged.

Validation

  • PYTHONPATH=. python3.11 -m pytest tests/fast/examples/experimental/verifiers/test_run.py -q --confcutdir=tests/fast/examples/experimental/verifiers: 4 passed
  • python3 -m py_compile tests/e2e/long/test_qwen3_0.6B_verifiers.py: passed
  • PYTHONPATH=. python3 tests/ci/run_suite.py --hw cuda --suite stage-c-2-gpu-h200 --match-all-labels --list-only: test enabled
  • uvx --python 3.11 pre-commit run --files tests/e2e/long/test_qwen3_0.6B_verifiers.py: passed
  • git diff --check: passed

The 2xH200 E2E has not run on this fork. Maintainers, please approve the held CI run so the default adapter is exercised before merge.

Tracking

Closes #2560

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Verifiers e2e covers only the legacy rollout path; the default VerifiersRolloutFn has no end-to-end coverage

1 participant