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)
58 lines
1.7 KiB
Bash
58 lines
1.7 KiB
Bash
source common.sh
|
|
|
|
clearStore
|
|
|
|
path=$(nix-store -q $(nix-instantiate fixed.nix -A good.0))
|
|
|
|
echo 'testing bad...'
|
|
nix-build fixed.nix -A bad --no-out-link && fail "should fail"
|
|
|
|
# Building with the bad hash should produce the "good" output path as
|
|
# a side-effect.
|
|
[[ -e $path ]]
|
|
nix path-info --json $path | grep fixed:md5:2qk15sxzzjlnpjk9brn7j8ppcd
|
|
|
|
echo 'testing good...'
|
|
nix-build fixed.nix -A good --no-out-link
|
|
|
|
if isDaemonNewer "2.4pre20210927"; then
|
|
echo 'testing --check...'
|
|
nix-build fixed.nix -A check --check && fail "should fail"
|
|
fi
|
|
|
|
echo 'testing good2...'
|
|
nix-build fixed.nix -A good2 --no-out-link
|
|
|
|
echo 'testing reallyBad...'
|
|
nix-instantiate fixed.nix -A reallyBad && fail "should fail"
|
|
|
|
# While we're at it, check attribute selection a bit more.
|
|
echo 'testing attribute selection...'
|
|
test $(nix-instantiate fixed.nix -A good.1 | wc -l) = 1
|
|
|
|
# Test parallel builds of derivations that produce the same output.
|
|
# Only one should run at the same time.
|
|
echo 'testing parallelSame...'
|
|
clearStore
|
|
nix-build fixed.nix -A parallelSame --no-out-link -j2
|
|
|
|
# Fixed-output derivations with a recursive SHA-256 hash should
|
|
# produce the same path as "nix-store --add".
|
|
echo 'testing sameAsAdd...'
|
|
out=$(nix-build fixed.nix -A sameAsAdd --no-out-link)
|
|
|
|
# This is what fixed.builder2 produces...
|
|
rm -rf $TEST_ROOT/fixed
|
|
mkdir $TEST_ROOT/fixed
|
|
mkdir $TEST_ROOT/fixed/bla
|
|
echo "Hello World!" > $TEST_ROOT/fixed/foo
|
|
ln -s foo $TEST_ROOT/fixed/bar
|
|
|
|
out2=$(nix-store --add $TEST_ROOT/fixed)
|
|
[ "$out" = "$out2" ]
|
|
|
|
out3=$(nix-store --add-fixed --recursive sha256 $TEST_ROOT/fixed)
|
|
[ "$out" = "$out3" ]
|
|
|
|
out4=$(nix-store --print-fixed-path --recursive sha256 "1ixr6yd3297ciyp9im522dfxpqbkhcw0pylkb2aab915278fqaik" fixed)
|
|
[ "$out" = "$out4" ]
|