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)
36 lines
978 B
Bash
36 lines
978 B
Bash
source common.sh
|
|
|
|
clearStore
|
|
clearCache
|
|
|
|
nix-store --generate-binary-cache-key cache1.example.org $TEST_ROOT/sk1 $TEST_ROOT/pk1
|
|
pk1=$(cat $TEST_ROOT/pk1)
|
|
|
|
export REMOTE_STORE_DIR="$TEST_ROOT/remote_store"
|
|
export REMOTE_STORE="file://$REMOTE_STORE_DIR"
|
|
|
|
ensureCorrectlyCopied () {
|
|
attrPath="$1"
|
|
nix build --store "$REMOTE_STORE" --file ./content-addressed.nix "$attrPath"
|
|
}
|
|
|
|
testOneCopy () {
|
|
clearStore
|
|
rm -rf "$REMOTE_STORE_DIR"
|
|
|
|
attrPath="$1"
|
|
nix copy -vvvv --to $REMOTE_STORE "$attrPath" --file ./content-addressed.nix \
|
|
--secret-key-files "$TEST_ROOT/sk1" --show-trace
|
|
|
|
ensureCorrectlyCopied "$attrPath"
|
|
|
|
# Ensure that we can copy back what we put in the store
|
|
clearStore
|
|
nix copy --from $REMOTE_STORE \
|
|
--file ./content-addressed.nix "$attrPath" \
|
|
--trusted-public-keys $pk1
|
|
}
|
|
|
|
for attrPath in rootCA dependentCA transitivelyDependentCA dependentNonCA dependentFixedOutput; do
|
|
testOneCopy "$attrPath"
|
|
done
|