Skip to content

fix: fetch sharded node compat reports#9

Merged
bartlomieju merged 2 commits into
mainfrom
fix/sharded-report-fetching
Apr 25, 2026
Merged

fix: fetch sharded node compat reports#9
bartlomieju merged 2 commits into
mainfrom
fix/sharded-report-fetching

Conversation

@bartlomieju
Copy link
Copy Markdown
Member

Summary

  • After ci: shard node_compat tests into 3 parallel jobs deno#33298, CI uploads node compat reports as 3 sharded files per OS (report-{os}-0.json.gz, report-{os}-1.json.gz, report-{os}-2.json.gz) instead of a single report-{os}.json.gz
  • The viewer was still fetching the old single-file URL, getting 404s for any date after the sharding change (e.g. /results/2026-04-24 returns no data)
  • Updates fetchReport to fetch all 3 shards and merge their results, with fallback to the old unsharded URL for historical data

Test plan

  • Verify /results/2026-04-24 (post-sharding date) loads correctly after deploy
  • Verify older dates (e.g. /results/2026-04-22) still work via the unsharded fallback

After denoland/deno#33298, CI uploads reports as sharded files
(report-{os}-{shard_index}.json.gz) instead of a single file per OS.
This updates fetchReport to fetch all 3 shards and merge them, with
fallback to the old unsharded URL for historical data.
@bartlomieju bartlomieju merged commit 5e68f8d into main Apr 25, 2026
5 checks passed
@bartlomieju bartlomieju deleted the fix/sharded-report-fetching branch April 25, 2026 05:56
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.

1 participant