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)
30 lines
814 B
Bash
30 lines
814 B
Bash
source common.sh
|
|
|
|
enableFeatures "daemon-trust-override"
|
|
|
|
restartDaemon
|
|
|
|
[[ $busybox =~ busybox ]] || skipTest "no busybox"
|
|
|
|
unset NIX_STORE_DIR
|
|
unset NIX_STATE_DIR
|
|
|
|
# We first build a dependency of the derivation we eventually want to
|
|
# build.
|
|
nix-build build-hook.nix -A passthru.input2 \
|
|
-o "$TEST_ROOT/input2" \
|
|
--arg busybox "$busybox" \
|
|
--store "$TEST_ROOT/local" \
|
|
--option system-features bar
|
|
|
|
# Now when we go to build that downstream derivation, Nix will try to
|
|
# copy our already-build `input2` to the remote store. That store object
|
|
# is input-addressed, so this will fail.
|
|
|
|
file=build-hook.nix
|
|
prog=$(readlink -e ./nix-daemon-untrusting.sh)
|
|
proto=ssh-ng
|
|
|
|
expectStderr 1 source build-remote-trustless.sh \
|
|
| grepQuiet "cannot add path '[^ ]*' because it lacks a signature by a trusted key"
|