mirror of
https://github.com/privatevoid-net/nix-super.git
synced 2024-11-13 01:36:15 +02:00
735a672e1f
Grouping our tests should make it easier to understand the intent than one long poorly-arranged list. It also is convenient for running just the tests for a specific component when working on that component. We need at least one test group so this isn't dead code; I decided to collect the tests for the `ca-derivations` and `dynamic-derivations` experimental features in groups. Do ```bash make ca.test-group -jN ``` and ```bash make dyn-drv.test-group -jN ``` to try running just them. I originally did this as part of #8397 for being able to just the local overlay store alone. I am PRing it separately now so we can separate general infra from new features. |
||
|---|---|---|
| .. | ||
| build-dry.sh | ||
| build-with-garbage-path.sh | ||
| build.sh | ||
| common.sh | ||
| concurrent-builds.sh | ||
| config.nix.in | ||
| content-addressed.nix | ||
| derivation-json.sh | ||
| duplicate-realisation-in-closure.sh | ||
| flake.nix | ||
| gc.sh | ||
| import-derivation.sh | ||
| local.mk | ||
| new-build-cmd.sh | ||
| nix-copy.sh | ||
| nix-run.sh | ||
| nix-shell.sh | ||
| nondeterministic.nix | ||
| post-hook.sh | ||
| racy.nix | ||
| recursive.sh | ||
| repl.sh | ||
| selfref-gc.sh | ||
| signatures.sh | ||
| substitute.sh | ||
| why-depends.sh | ||