Conversation
A workflow step running after the benchmarks had no way to know which CodSpeed run the results were uploaded to. After a successful upload on GitHub Actions, write it to `$GITHUB_OUTPUT` as `run-id`. All uploads of a workflow run share the same CodSpeed run, so the id of the last upload is the run id. A failure to write the output only warns. Closes COD-3661 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merging this PR will degrade performance by 17.56%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | WallTime | memtrack track tar |
8 s | 9.7 s | -17.56% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing cod-3661-expose-the-run-id-as-an-output-of-the-runner-and-the-github (9ac0bbb) with main (7c135cc)
Footnotes
-
4 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
Writing to `$GITHUB_OUTPUT` on every upload would add a `run-id` output to any user `run:` step invoking the runner. Gate it behind `--export-run-id` / `CODSPEED_EXPORT_RUN_ID`, set by the CodSpeed action. Refs COD-3661 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Now that the export is opt-in, a missing `$GITHUB_OUTPUT` means the caller asked for a `run-id` output that will never be written. Surface it as a warning instead of silently skipping. Refs COD-3661 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
After a successful upload on GitHub Actions, write the CodSpeed run id to
$GITHUB_OUTPUTasrun-id, so later workflow steps can read the run back instead of guessing it from the commit and branch.All uploads of a workflow run land in the same CodSpeed run, so the id of the last upload is the run id. Failing to write the output only logs a warning.
The action will expose it as a
run-idoutput once this is released.Closes COD-3661