Skip to content
Shard Timings Refresh

ci: hourly full run on main, push narrows to the affected set, and a filer for a red one #5

Sign in to view logs

ci: hourly full run on main, push narrows to the affected set, and a filer for a red one

ci: hourly full run on main, push narrows to the affected set, and a filer for a red one #5

Triggered via pull request September 9, 2026 00:25
@baozhoutaobaozhoutao
synchronize #16991
claude/issue-16467-hourly-full-run
Status Success
Total duration 32s
Artifacts –

shard-timings-refresh.yml

on: pull_request
Regenerate the shard-timings dataset
29s
Regenerate the shard-timings dataset
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Regenerate the shard-timings dataset
Shard timings NOT MEASURED: no completed `schedule` run of ci.yml exists on main yet. The dataset was left untouched. If this repeats once the hourly full run has been live for a few hours, the trigger is gone or every hourly run is being cancelled — file it.