Skip to content

The hooks job leaves the engine's tests and clippy to the engine job #459

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HackingGate merged 1 commit into from
Oct 29, 2026
Merged

The hooks job leaves the engine's tests and clippy to the engine job #459

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion .github/workflows/test.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,10 +179,14 @@ jobs:
# survives; running it once per runner here would build the tree
# instrumented three more times to answer the same question. The Kani
# proofs are skipped for the same reason, and have a job of their own below.
# So are the engine's tests and clippy, which the `engine` job runs on the
# same commit: ubuntu-slim cancels a job at its time cap, and building the
# test binaries a second time on its one CPU is what pushed the pre-commit
# leg past it. Their hook entries still run at every local pre-push.
# What this job asks is whether each runner can DRIVE the configuration,
# and the hooks left in it answer that.
env:
SKIP: coverage,kani
SKIP: coverage,kani,engine-tests,engine-clippy
# The private-name guards ask the forge whether a name is a private
# repository, and they ask through `gh`. With no token `gh` answers
# nothing -- and until an unaskable forge became its own state, that was
Expand Down
Loading