Skip to content

fix(ci): store the ROCm verification logs as text instead of tarballs - #2266

Merged
inureyes merged 1 commit into
mainfrom
fix/binary-assets-rocm-logs
Oct 11, 2026
Merged

inureyes merged 1 commit into
mainfrom
fix/binary-assets-rocm-logs

Conversation

@inureyes

Copy link
Copy Markdown
Member

Summary

The binary assets CI job has failed on main since PR #2250: it committed docs/benchmark_results/data/rocm-unified-engine-gfx1151-2026-10-08/guard/guard-logs.tar.gz (15.1 KB) and rounds/raw-logs.tar.gz (13.8 KB) without declaring them in scripts/ci/check_binary_assets.py, and every PR merged since carried the same failure.

Both archives contain only plain-text run logs (212 files), so this unpacks them in place instead of adding a binary exception:

  • guard/guard-logs.tar.gz becomes guard/logs/ (the guard's per-run logs, guard/ and rounds/guard/ inside it as archived).
  • rounds/raw-logs.tar.gz becomes rounds/raw/, the path rocm-unified-engine-gfx1151-2026-10-08.md already cites for the raw mlxcel-bench-decode output.
  • The report's reference to guard/guard-logs.tar.gz now points at guard/logs/.

Text diffs and delta-compresses in history, and the guard's 256 KB binary budget stays for assets that need to be binary. No log content changes.

Test plan

  • python3 scripts/ci/check_binary_assets.py: binary-assets: OK, 9 declared binary files, 63.3 KB of 256 KB budget
  • file reports every unpacked file as text; none is matched by .gitignore

PR #2250 committed docs/benchmark_results/data/rocm-unified-engine-gfx1151-2026-10-08/guard/guard-logs.tar.gz and rounds/raw-logs.tar.gz without declaring them in scripts/ci/check_binary_assets.py, so the binary assets job has failed on main and on every PR since. Both archives hold small plain-text run logs (212 files), so they are unpacked in place (guard/logs/ and rounds/raw/, the path the report already cites for the raw logs) instead of being declared as a binary exception: text diffs and delta-compresses, and the guard's binary budget stays for assets that need it. The report's guard-log reference now points at guard/logs/.
@inureyes inureyes added type:bug Bug fixes, error corrections, or issue resolutions priority:high High priority status:review Under review status:done Completed and removed status:review Under review labels Oct 11, 2026
@inureyes
inureyes merged commit c44e209 into main Oct 11, 2026
27 checks passed
inureyes added a commit that referenced this pull request Oct 11, 2026
…rballs (#2267)

## Summary

Follow-up to #2266. That PR cleared the `binary assets` failure from #2250 by unpacking the ROCm verification run logs into 212 text files. The logs are only opened to audit a run, so this keeps them archived instead:

- Restores `docs/benchmark_results/data/rocm-unified-engine-gfx1151-2026-10-08/guard/guard-logs.tar.gz` and `rounds/raw-logs.tar.gz`, byte-identical to #2250's, and removes the unpacked `guard/logs/` and `rounds/raw/`.
- Restores the report's reference to `guard/guard-logs.tar.gz`.
- Adds a `DECLARED` rule to `scripts/ci/check_binary_assets.py` for `docs/benchmark_results/data/*.tar.gz` (raw per-run logs behind a committed benchmark report), 32 KB per file.

## Test plan

- [x] `python3 scripts/ci/check_binary_assets.py`: OK, 11 declared binary files, 92.2 KB of the 256 KB budget
- [x] `scripts/ci/check_binary_assets_test.sh`: all cases pass
- [x] `scripts/insert_apache_header.py --check`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority:high High priority status:done Completed type:bug Bug fixes, error corrections, or issue resolutions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant