resultChecks.enable
Enable Result monad checks.
Type: boolean
Default:
true
resultChecks.enableFlakeChecks
Whether to add an aggregate Result check to flake.checks.
The single resultChecks flake check depends on every
derivation check (built in parallel by the scheduler) and
bakes in eval check verdicts. Its log carries the full
per-check report; it fails if any check failed.
Type: boolean
Default:
true
resultChecks.checks
Checks to run.
Values are a derivation (flat check), an attrset of
derivations (suite), or an eval check (mkEval). Suite
and eval checks are grouped under a named header in the
TUI and keyed as "suite:name" in reports.
Type: attribute set of (package or (eval check (mkEval)) or attribute set of package)
Default:
{ }
resultChecks.evalChecks
Per-test result entries of all eval checks, keyed by check then test name. Entries are computed lazily so runners can force them in parallel (e.g. via nix-eval-jobs).
Type: lazy attribute set of lazy attribute set of raw value (read only)
Default:
pkgs.resultChecks.mkEvalChecks cfg.checks
resultChecks.report
The generated report package.
Covers derivation checks only; eval check results are
exposed through evalChecks so that runners can evaluate
them in parallel without the report forcing them.
Type: package (read only)
Default:
pkgs.resultChecks.mkReport cfg.checks
resultChecks.skipChecks
Check keys to skip.
Flat checks are identified by name (e.g. "lint").
Suite checks and eval tests are identified as
"suite:name" (e.g. "db:schema").
Skipped derivation checks are replaced with placeholder derivations; skipped eval tests are never evaluated. Both are marked as skipped in the report.
Type: list of string
Default:
[ ]