Skip to content

Fix robust-mts-attack rolling test grouping - #3311

Open
kiwoongyoon wants to merge 2 commits into
awslabs:devfrom
kiwoongyoon:gitcontribute/20260703-072204-695124-awslabs-gluonts-issue-3275
Open

Fix robust-mts-attack rolling test grouping#3311
kiwoongyoon wants to merge 2 commits into
awslabs:devfrom
kiwoongyoon:gitcontribute/20260703-072204-695124-awslabs-gluonts-issue-3275

Conversation

@kiwoongyoon

Copy link
Copy Markdown

Title: Fix robust-mts-attack rolling test grouping

Summary

  • Split robust-mts-attack rolling test entries by evaluation date before stacking them, avoiding NumPy ragged-array conversion failures.
  • Update the nursery grouper's date handling to work with current GluonTS Period starts.
  • Add a targeted regression test for rolling test dates with different left-padded lengths.

Issue snapshot duplicate-work check: #3275 is unassigned, has no duplicate/blocking labels, and mentions no related PR.

Fixes #3275

Test evidence

  • PYTHONPATH=src pytest -q test/nursery/robust_mts_attack/test_grouper.py passed: 1 passed in 0.01s
  • git diff --check passed

Risks or notes for maintainers

  • The change is limited to nursery robust-mts-attack code and one focused test.
  • It preserves the existing assumption that rolling test entries are ordered by test date.
  • Full traffic dataset training was not run because the issue did not include the exact command or dataset setup.

@kiwoongyoon
kiwoongyoon marked this pull request as ready for review August 10, 2026 16:58
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.

robust-mts-attack repoducing has problem

1 participant