Repository navigation
Conversation
Signed-off-by: Serge Panev <spanev@nvidia.com>
yaoyu-33
added
area:environment
github-actions
Bot
added
the
sla:triage-overdue
khazic
pushed a commit
to khazic/Gym-lao
that referenced
this pull request
Oct 6, 2026
GDPVal currently prints transient judge failures such as HTTP 429 responses, but loses the request shape and whether a later retry recovered. This adds opt-in structured telemetry through `judge_telemetry_output_dir`, recording preflight exclusions, individual provider failures, retry recovery, invalid responses, and terminal matchup failures. Each resources-server process writes its own JSONL file. Failure events include the task/reference/judge identity plus the actual transmitted file labels, types, counts, attachment sizes, request size, and transport limits. Compact completion events provide the denominator needed to calculate failure and recovery rates. Prompts, attachment contents, base64 payloads, credentials, and absolute paths are excluded, and telemetry write failures never affect judging. The included summarizer reports failure classes, HTTP statuses, recovery and terminal-failure rates, preflight reasons, request-size buckets, judges, tasks, and file extensions: ```bash python -m resources_servers.gdpval.judge_telemetry /path/to/judge_telemetry ``` Judging behavior, retries, routing, scoring, and ELO fitting are unchanged when telemetry is disabled or enabled. Ports NVIDIA-NeMo#3960 from `gdpval-devel` to main; it applies without conflicts. Validation: - `resources_servers/gdpval/tests`: 570 passed on main `10b38dbfd` plus this change - `ruff check` and `ruff format --check` clean Signed-off-by: Serge Panev <spanev@nvidia.com> Co-authored-by: Marta Stepniewska-Dziubinska <marta-sd@users.noreply.github.com>
This was referenced Oct 22, 2026
This branch has not been deployed
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.
GDPVal currently prints transient judge failures such as HTTP 429 responses, but loses the request shape and whether a later retry recovered. This adds opt-in structured telemetry through
judge_telemetry_output_dir, recording preflight exclusions, individual provider failures, retry recovery, invalid responses, and terminal matchup failures.Each resources-server process writes its own JSONL file. Failure events include the task/reference/judge identity plus the actual transmitted file labels, types, counts, attachment sizes, request size, and transport limits. Compact completion events provide the denominator needed to calculate failure and recovery rates. Prompts, attachment contents, base64 payloads, credentials, and absolute paths are excluded, and telemetry write failures never affect judging.
The included summarizer reports failure classes, HTTP statuses, recovery and terminal-failure rates, preflight reasons, request-size buckets, judges, tasks, and file extensions:
Judging behavior, retries, routing, scoring, and ELO fitting are unchanged when telemetry is disabled or enabled.
Validation:
gdpval-devel