CI and devshell comments say what the config does: jobTimeout bounds jobs, coverage runs nightly, dead timeout keys removed
Job-level timeout-minutes is parsed but not enforced by this runner; only the runner's jobTimeout bounds a job. Also fixes the devshell coverage comment, the shellcheck job comment, an option description citing a script that is not in the repo, and comment file pointers that resolve to nothing.
This commit is contained in:
parent
fefc565794
commit
2644c0d5f9
7 changed files with 20 additions and 27 deletions
|
|
@ -5,7 +5,7 @@ name: coverage
|
|||
#
|
||||
# ⚠️ The hour is deliberate: at the default job capacity of 1
|
||||
# (`services.hyperhive.deploy.ci-runner.concurrency`) this job holds the
|
||||
# runner for its whole timeout and everything else queues behind it.
|
||||
# runner for its whole run and everything else queues behind it.
|
||||
#
|
||||
# Separate from ci.yml because a `workflow_dispatch` trigger there fires every
|
||||
# job in that file, and this must not run per pull request.
|
||||
|
|
@ -19,10 +19,9 @@ jobs:
|
|||
name: cargo llvm-cov
|
||||
if: vars.PUBLIC_FORGE != 'true'
|
||||
runs-on: ${{ vars.PUBLIC_FORGE == 'true' && 'nixos' || 'hive-ci' }}
|
||||
# Above the 30 min `nix flake check` allows, because instrumented
|
||||
# builds are slower than the ordinary ones and this starts from a
|
||||
# cache that the normal jobs never populate.
|
||||
timeout-minutes: 60
|
||||
# Instrumented builds are slower than the ordinary ones and this starts
|
||||
# from a cache that the normal jobs never populate. The runner's
|
||||
# `jobTimeout` (default 1h) is the only bound; a longer run is killed.
|
||||
steps:
|
||||
- uses: actions/checkout@v3
|
||||
- name: coverage
|
||||
|
|
|
|||
Loading…
Reference in a new issue