30dcc19d1f
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/ ``` (cherry picked from commit 68c81c737571794f7246db53fb4774e94fcf4b7e)
50 lines
857 B
Bash
50 lines
857 B
Bash
# Test circular flake dependencies.
|
|
source ./common.sh
|
|
|
|
requireGit
|
|
|
|
flakeA=$TEST_ROOT/flakeA
|
|
flakeB=$TEST_ROOT/flakeB
|
|
|
|
createGitRepo $flakeA
|
|
createGitRepo $flakeB
|
|
|
|
cat > $flakeA/flake.nix <<EOF
|
|
{
|
|
inputs.b.url = git+file://$flakeB;
|
|
inputs.b.inputs.a.follows = "/";
|
|
|
|
outputs = { self, b }: {
|
|
foo = 123 + b.bar;
|
|
xyzzy = 1000;
|
|
};
|
|
}
|
|
EOF
|
|
|
|
git -C $flakeA add flake.nix
|
|
|
|
cat > $flakeB/flake.nix <<EOF
|
|
{
|
|
inputs.a.url = git+file://$flakeA;
|
|
|
|
outputs = { self, a }: {
|
|
bar = 456 + a.xyzzy;
|
|
};
|
|
}
|
|
EOF
|
|
|
|
git -C $flakeB add flake.nix
|
|
git -C $flakeB commit -a -m 'Foo'
|
|
|
|
[[ $(nix eval $flakeA#foo) = 1579 ]]
|
|
[[ $(nix eval $flakeA#foo) = 1579 ]]
|
|
|
|
sed -i $flakeB/flake.nix -e 's/456/789/'
|
|
git -C $flakeB commit -a -m 'Foo'
|
|
|
|
[[ $(nix eval --update-input b $flakeA#foo) = 1912 ]]
|
|
|
|
# Test list-inputs with circular dependencies
|
|
nix flake metadata $flakeA
|
|
|