ci: maintain pipeline-bench report in PR description + comment reactions - #2145
Merged
Merged
Conversation
Move the Tokenizer-vs-PipelineTokenizer report out of a PR comment and into a marker-delimited section of the PR description, kept current in place (upsert_pr_section.py). Pushes to feat/train_encode_split now target PR #2119; /pipeline-bench dispatch targets its own PR. Add emoji feedback to the comment-triggered flow: 馃憖 when the trigger fires, 馃憤 from the bench workflow on success. Add a cancel-in-progress concurrency group keyed on github.ref so a newer commit/comment supersedes an in-flight run for the same target without cancelling other PRs' benches. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
ArthurZucker
pushed a commit
that referenced
this pull request
Sep 2, 2026
Superseded by the standalone tokbench repo; not part of rc0. Squashed from 4 commits: - ci: Simple bench workflow for PipelineTokenizer (#2141) - ci: maintain pipeline-bench report in PR description + comment reactions (#2145) - ci: label-triggered pipeline bench into the PR description (#2146) - ci: run benches on more tokenizers (#2147) Area: ci-bench
ArthurZucker
pushed a commit
that referenced
this pull request
Sep 2, 2026
Part of the pipeline benchmark programme (6,694 lines over 26 commits). The harness was later extracted to the standalone tokbench repo and is not part of the rc0 tree. Squashed from 4 commits: - ci: Simple bench workflow for PipelineTokenizer (#2141) - ci: maintain pipeline-bench report in PR description + comment reactions (#2145) - ci: label-triggered pipeline bench into the PR description (#2146) - ci: run benches on more tokenizers (#2147) Area: ci-bench
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move the Tokenizer-vs-PipelineTokenizer report out of a PR comment and into a marker-delimited section of the PR description, kept current in place (upsert_pr_section.py). Pushes to feat/train_encode_split now target PR #2119; /pipeline-bench dispatch targets its own PR.
Add emoji feedback to the comment-triggered flow: 馃憖 when the trigger fires, 馃憤 from the bench workflow on success. Add a cancel-in-progress concurrency group keyed on github.ref so a newer commit/comment supersedes an in-flight run for the same target without cancelling other PRs' benches.