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/ ```
29 lines
580 B
Bash
29 lines
580 B
Bash
source common.sh
|
|
|
|
path1=$(nix-store --add ./dummy)
|
|
echo $path1
|
|
|
|
path2=$(nix-store --add-fixed sha256 --recursive ./dummy)
|
|
echo $path2
|
|
|
|
if test "$path1" != "$path2"; then
|
|
echo "nix-store --add and --add-fixed mismatch"
|
|
exit 1
|
|
fi
|
|
|
|
path3=$(nix-store --add-fixed sha256 ./dummy)
|
|
echo $path3
|
|
test "$path1" != "$path3" || exit 1
|
|
|
|
path4=$(nix-store --add-fixed sha1 --recursive ./dummy)
|
|
echo $path4
|
|
test "$path1" != "$path4" || exit 1
|
|
|
|
hash1=$(nix-store -q --hash $path1)
|
|
echo $hash1
|
|
|
|
hash2=$(nix-hash --type sha256 --base32 ./dummy)
|
|
echo $hash2
|
|
|
|
test "$hash1" = "sha256:$hash2"
|