lix-releng-staging/tests/init.sh

# Don't start the daemon
source common/vars-and-functions.sh

test -n "$TEST_ROOT"
if test -d "$TEST_ROOT"; then
    chmod -R u+w "$TEST_ROOT"
    # We would delete any daemon socket, so let's stop the daemon first.
    killDaemon
    rm -rf "$TEST_ROOT"
fi
mkdir "$TEST_ROOT"

mkdir "$NIX_STORE_DIR"
mkdir "$NIX_LOCALSTATE_DIR"
mkdir -p "$NIX_LOG_DIR"/drvs
mkdir "$NIX_STATE_DIR"
mkdir "$NIX_CONF_DIR"

cat > "$NIX_CONF_DIR"/nix.conf <<EOF
build-users-group =
keep-derivations = false
sandbox = false
experimental-features = nix-command flakes
gc-reserved-space = 0
substituters =
flake-registry = $TEST_ROOT/registry.json
show-trace = true
include nix.conf.extra
trusted-users = $(whoami)
EOF

cat > "$NIX_CONF_DIR"/nix.conf.extra <<EOF
fsync-metadata = false
!include nix.conf.extra.not-there
EOF

# Initialise the database.
nix-store --init

# Did anything happen?
test -e "$NIX_STATE_DIR"/db/db.sqlite
Clean up daemon handling Split `common.sh` into the vars and functions definitions vs starting the daemon (and possibly other initialization logic). This way, `init.sh` can just `source` the former. Trying to start the daemon before `nix.conf` is written will fail because `nix daemon` requires `--experimental-features 'nix-command'`. `killDaemon` is idempotent, so it's safe to call when no daemon is running. `startDaemon` and `killDaemon` use the PID (which is now exported to subshells) to decide whether there is work to be done, rather than `NIX_REMOTE`, which might conceivably be set differently even if a daemon is running. `startDaemon` and `killDaemon` can save/restore the old `NIX_REMOTE` as `NIX_REMOTE_OLD`. `init.sh` kills daemon before deleting everything (including the daemon socket). 2021-12-09 15:16:18 +00:00			`# Don't start the daemon`
			`source common/vars-and-functions.sh`
* Make it easy to run individual tests from the command line. 2006-03-01 12:15:33 +00:00
* Allow the location of the store etc. to be specified using environment variables. * Started adding some automatic tests. * Do a `make check' when building RPMs. 2004-05-04 12:15:30 +00:00			`test -n "$TEST_ROOT"`
			`if test -d "$TEST_ROOT"; then`
			`chmod -R u+w "$TEST_ROOT"`
Make init.sh safe to run twice `init.sh` is tested on its own. We used to do that. I deleted it in 4720853129b6866775edd9f90ad6f10701f98a3c but I am not sure why. Better to just restore it; at one point working on this every other test passed, so seems good to check whether `init.sh` can be run twice. We don't need to run `init.sh` twice, but I want to try to make our tests as robust as possible so that manual debugging (where tests for better or worse might be run ways that we didn't expect) is less fragile. 2021-12-09 15:16:18 +00:00			`# We would delete any daemon socket, so let's stop the daemon first.`
Clean up daemon handling Split `common.sh` into the vars and functions definitions vs starting the daemon (and possibly other initialization logic). This way, `init.sh` can just `source` the former. Trying to start the daemon before `nix.conf` is written will fail because `nix daemon` requires `--experimental-features 'nix-command'`. `killDaemon` is idempotent, so it's safe to call when no daemon is running. `startDaemon` and `killDaemon` use the PID (which is now exported to subshells) to decide whether there is work to be done, rather than `NIX_REMOTE`, which might conceivably be set differently even if a daemon is running. `startDaemon` and `killDaemon` can save/restore the old `NIX_REMOTE` as `NIX_REMOTE_OLD`. `init.sh` kills daemon before deleting everything (including the daemon socket). 2021-12-09 15:16:18 +00:00			`killDaemon`
* Allow the location of the store etc. to be specified using environment variables. * Started adding some automatic tests. * Do a `make check' when building RPMs. 2004-05-04 12:15:30 +00:00			`rm -rf "$TEST_ROOT"`
			`fi`
			`mkdir "$TEST_ROOT"`

			`mkdir "$NIX_STORE_DIR"`
* Make check fixes. 2005-02-01 17:50:48 +00:00			`mkdir "$NIX_LOCALSTATE_DIR"`
* `make check' fix. 2005-02-18 08:40:52 +00:00			`mkdir -p "$NIX_LOG_DIR"/drvs`
* Allow the location of the store etc. to be specified using environment variables. * Started adding some automatic tests. * Do a `make check' when building RPMs. 2004-05-04 12:15:30 +00:00			`mkdir "$NIX_STATE_DIR"`
* Fix broken GC test. 2005-02-15 09:39:12 +00:00			`mkdir "$NIX_CONF_DIR"`
* Allow the location of the store etc. to be specified using environment variables. * Started adding some automatic tests. * Do a `make check' when building RPMs. 2004-05-04 12:15:30 +00:00
* Fix broken GC test. 2005-02-15 09:39:12 +00:00			`cat > "$NIX_CONF_DIR"/nix.conf <<EOF`
Fix Debian tests These actually run as root in a VM, so they get confused. http://hydra.nixos.org/build/10775854 2014-05-02 17:02:10 +00:00			`build-users-group =`
Rename a few configuration options In particular, drop the "build-" and "gc-" prefixes which are pointless. So now you can say nix build --no-sandbox instead of nix build --no-build-use-sandbox 2017-08-31 12:28:25 +00:00			`keep-derivations = false`
Enable sandboxing by default Closes #179. 2018-11-07 16:08:28 +00:00			`sandbox = false`
Add experimental-features setting Experimental features are now opt-in. There are currently two experimental features: "nix-command" (which enables the "nix" command), and "flakes" (which enables support for flakes). This will allow us to merge experimental features more quickly, without committing to supporting them indefinitely. Typical usage: $ nix build --experimental-features 'nix-command flakes' nixpkgs#hello 2019-10-16 15:45:09 +00:00			`experimental-features = nix-command flakes`
Set gc-reserved-space to 0 in tests This reduces the amount of disk space needed to run the tests from half a gigabyte to 10 megabytes. 2020-07-02 14:37:30 +00:00			`gc-reserved-space = 0`
Use no substituers by default in the tests Otherwise https://cache.nixos.org is chosen by default, causing the OSX testsuite to hang inside the sandbox. (In a way, this is probably rugging an actual bug under the carpet as Nix should be able to gracefully timeout in such a case, but that's beyond mac OSX-fu) 2020-12-09 13:53:45 +00:00			`substituters =`
Simplify flake tests 2020-01-28 15:34:37 +00:00			`flake-registry = $TEST_ROOT/registry.json`
Add a trace to readLine() failures Hopefully this helps to diagnose 'error: unexpected EOF reading a line' on macOS. 2021-02-05 11:11:50 +00:00			`show-trace = true`
Allow includes from nix.conf 2018-02-13 13:16:32 +00:00			`include nix.conf.extra`
Allow running all the tests with the daemon When `NIX_DAEMON_PACKAGE` is set, make all the tests use the Nix daemon. That way we can test every piece of Nix functionality both with and without the daemon. Tests for which using the daemon isn’t possible or doesn’t make sens can selectively be disabled with `needLocalStore` 2021-07-26 04:54:55 +00:00			`trusted-users = $(whoami)`
Allow includes from nix.conf 2018-02-13 13:16:32 +00:00			`EOF`

			`cat > "$NIX_CONF_DIR"/nix.conf.extra <<EOF`
* Disable fsync() in SQLite if the fsync-metadata option is set to false. * Change the default for `fsync-metadata' to true. * Disable `fsync-metadata' in `make check'. 2010-02-24 13:12:57 +00:00			`fsync-metadata = false`
Allow includes from nix.conf 2018-02-13 13:16:32 +00:00			`!include nix.conf.extra.not-there`
* Fix broken GC test. 2005-02-15 09:39:12 +00:00			`EOF`

* Allow the location of the store etc. to be specified using environment variables. * Started adding some automatic tests. * Do a `make check' when building RPMs. 2004-05-04 12:15:30 +00:00			`# Initialise the database.`
* Refactoring: remove unnecessary variables from the tests. 2011-10-10 21:32:34 +00:00			`nix-store --init`
* Allow the location of the store etc. to be specified using environment variables. * Started adding some automatic tests. * Do a `make check' when building RPMs. 2004-05-04 12:15:30 +00:00
			`# Did anything happen?`
Remove $NIX_DB_DIR This variable has no reason to exist, given $NIX_STATE_DIR. 2016-07-27 15:14:41 +00:00			`test -e "$NIX_STATE_DIR"/db/db.sqlite`