68c81c7375
I think it is bad for these reasons when `tests/` contains a mix of functional and integration tests - Concepts is harder to understand, the documentation makes a good unit vs functional vs integration distinction, but when the integration tests are just two subdirs within `tests/` this is not clear. - Source filtering in the `flake.nix` is more complex. We need to filter out some of the dirs from `tests/`, rather than simply pick the dirs we want and take all of them. This is a good sign the structure of what we are trying to do is not matching the structure of the files. With this change we have a clean: ```shell-session $ git show 'HEAD:tests' tree HEAD:tests functional/ installer/ nixos/ ```
31 lines
765 B
Nix
31 lines
765 B
Nix
let
|
|
contentAddressedByDefault = builtins.getEnv "NIX_TESTS_CA_BY_DEFAULT" == "1";
|
|
caArgs = if contentAddressedByDefault then {
|
|
__contentAddressed = true;
|
|
outputHashMode = "recursive";
|
|
outputHashAlgo = "sha256";
|
|
} else {};
|
|
in
|
|
|
|
rec {
|
|
shell = "@bash@";
|
|
|
|
path = "@coreutils@";
|
|
|
|
system = "@system@";
|
|
|
|
shared = builtins.getEnv "_NIX_TEST_SHARED";
|
|
|
|
mkDerivation = args:
|
|
derivation ({
|
|
inherit system;
|
|
builder = shell;
|
|
args = ["-e" args.builder or (builtins.toFile "builder-${args.name}.sh" ''
|
|
if [ -e "$NIX_ATTRS_SH_FILE" ]; then source $NIX_ATTRS_SH_FILE; fi;
|
|
eval "$buildCommand"
|
|
'')];
|
|
PATH = path;
|
|
} // caArgs // removeAttrs args ["builder" "meta"])
|
|
// { meta = args.meta or {}; };
|
|
}
|