Skip to content

test: benchmark skip-semantics probe (will be closed) - #29

Closed
alejoamiras wants to merge 2 commits into
ci/benchmark-paths-filterfrom
test/benchmark-filter-skip
Closed

test: benchmark skip-semantics probe (will be closed)#29
alejoamiras wants to merge 2 commits into
ci/benchmark-paths-filterfrom
test/benchmark-filter-skip

Conversation

@alejoamiras

Copy link
Copy Markdown
Collaborator

Throwaway docs-only PR to observe whether the gated benchmark job reports as skipped or disappears from the checks list. Will be closed without merging.

🤖 Generated with Claude Code

alejoamiras and others added 2 commits August 18, 2026 16:14
Benchmark takes ~35 minutes and ran on every PR, docs-only included. A
changes job (dorny/paths-filter, SHA-pinned v3.0.2) now gates it on paths
that can affect benchmark output: contract sources, Nargo manifests, the
benchmark definitions, dependency manifests, and the workflow itself.

Job-level gating keeps a skipped benchmark reporting as passing for
branch protection, unlike workflow-level paths filtering which would
leave a required check pending forever.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@alejoamiras
alejoamiras force-pushed the ci/benchmark-paths-filter branch from c031fa5 to 193b550 Compare August 18, 2026 16:19
@alejoamiras

Copy link
Copy Markdown
Collaborator Author

Probe complete: with the filter gating, the caller job reports as a skipped 'benchmark' check and the nested 'benchmark / Benchmark' check is never created. Results incorporated into the main PR.

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