[ci] Reserve comments for stats and tests#93240
Conversation
Tests PassedCommit: a29f34e |
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles
Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📎 Tarball URLCommit: a29f34e |
This increases the chances of finding the comments in the same place: at the tippity top of the PR conversation.
75f81df to
fffc121
Compare
| const sha = pr.headSha || workflowRun.head_sha | ||
| const body = [ | ||
| STATS_COMMENT_MARKER, | ||
| '## Stats in progress', |
There was a problem hiding this comment.
Docs-only changes won't trigger the stats workflow, so we'd potentially end up in a state where there's a "Stats in progress" comment that is never fulfilled
There was a problem hiding this comment.
Right. Also did the same for build-and-test in case people cancel
There was a problem hiding this comment.
A docs-only Generate stats actually counts as success: https://github.com/vercel/next.js/actions/runs/24933442991/job/73014965795?pr=93243 -> https://api.github.com/repos/vercel/next.js/actions/runs/24933442991
There was a problem hiding this comment.
It has conclusion: success, but the aggregate/post step is skipped.
So when the reporter handles the completed run, it enters handleStatsWorkflow, sees it was not cancelled, scans the aggregate logs, finds no --stats start-- block, and returns without updating the existing in progress placeholder
34ab3a6 to
772eec5
Compare
772eec5 to
a29f34e
Compare
This increases the chances of finding the comments in the same place: at the tippity top of the PR conversation.