nordic-dev.net/nix
nordic-dev.net/nix
2
0
Fork 0
mirror of https://github.com/NixOS/nix.git synced 2024-11-22 14:52:55 +00:00
Code Issues Packages Projects Releases Wiki Activity
278e02c0ef
nix/tests/functional/user-envs.sh

198 lines
6.1 KiB
Bash
Raw Normal View History

* Make it easy to run individual tests from the command line.
2006-03-01 12:15:33 +00:00
source common.sh
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
if [ -z "${storeCleared-}" ]; then
Remove $NIX_DB_DIR This variable has no reason to exist, given $NIX_STATE_DIR.
2016-07-27 15:14:41 +00:00
clearStore
fi
* `nix-install-package --url': install from a URL (NIX-12). * `nix-install-package --help' (NIX-9). * `nix-install-package --non-interactive': don't prompt or pause. * Tests for nix-install-package. * Security fixes: filter the values obtained from the nixpkg.
2006-09-21 18:54:08 +00:00
clearProfiles
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Query installed: should be empty.
* Refactoring: remove unnecessary variables from the tests.
2011-10-10 21:32:34 +00:00
test "$(nix-env -p $profiles/test -q '*' | wc -l)" -eq 0
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
nix-env --switch-profile $profiles/test
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Query available: should contain several.
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
test "$(nix-env -f ./user-envs.nix -qa '*' | wc -l)" -eq 6
outPath10=$(nix-env -f ./user-envs.nix -qa --out-path --no-name '*' | grep foo-1.0)
drvPath10=$(nix-env -f ./user-envs.nix -qa --drv-path --no-name '*' | grep foo-1.0)
[ -n "$outPath10" -a -n "$drvPath10" ]
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
Add some tests for `nix-env -q --json`
2022-03-16 17:39:46 +00:00
# Query with json
nix-env -f ./user-envs.nix -qa --json | jq -e '.[] | select(.name == "bar-0.1") | [
.outputName == "out",
.outputs.out == null
] | all'
nix-env -f ./user-envs.nix -qa --json --out-path | jq -e '.[] | select(.name == "bar-0.1") | [
.outputName == "out",
(.outputs.out | test("'$NIX_STORE_DIR'.*-0\\.1"))
] | all'
`nix-env --query`: fix `--json` ignoring `--drv-path` ```json { "AMB-plugins": { "drvPath": "/nix/store/l99cb7h2hy8dg005arsjbd9kx0w05d3h-AMB-plugins-0.8.1.drv", "name": "AMB-plugins-0.8.1", "outputName": "out", "outputs": { "out": null }, "pname": "AMB-plugins", "system": "x86_64-linux", "version": "0.8.1" }, "ArchiSteamFarm": { "drvPath": "/nix/store/nhplgyjj34fz6hjmnyih25gxscfh8s7b-ArchiSteamFarm-5.4.12.5.drv", "name": "ArchiSteamFarm-5.4.12.5", "outputName": "out", "outputs": { "out": null }, "pname": "ArchiSteamFarm", "system": "x86_64-linux", "version": "5.4.12.5" }, ... ```
2023-10-30 23:36:13 +00:00
nix-env -f ./user-envs.nix -qa --json --drv-path | jq -e '.[] | select(.name == "bar-0.1") | (.drvPath | test("'$NIX_STORE_DIR'.*-0\\.1\\.drv"))'
Add some tests for `nix-env -q --json`
2022-03-16 17:39:46 +00:00
* `nix-env -qa --description' shows human-readable descriptions of packages (provided that they have a `meta.description' attribute). E.g., $ ./src/nix-env/nix-env -qa --description gcc gcc-4.0.2 GNU Compiler Collection, 4.0.x (cross-compiler for sparc-linux) gcc-4.0.2 GNU Compiler Collection, 4.0.x (cross-compiler for mips-linux) gcc-4.0.2 GNU Compiler Collection, 4.0.x (cross-compiler for arm-linux) gcc-4.0.2 GNU Compiler Collection, 4.0.x
2006-03-10 16:20:42 +00:00
# Query descriptions.
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -f ./user-envs.nix -qa '*' --description | grepQuiet silly
Remove world-writability from per-user directories 'nix-daemon' now creates subdirectories for users when they first connect. Fixes #509 (CVE-2019-17365). Should also fix #3127.
2019-10-09 16:01:21 +00:00
rm -rf $HOME/.nix-defexpr
Test ~/.nix-defexpr
2014-02-26 17:33:13 +00:00
ln -s $(pwd)/user-envs.nix $HOME/.nix-defexpr
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -qa '*' --description | grepQuiet silly
* `nix-env -qa --description' shows human-readable descriptions of packages (provided that they have a `meta.description' attribute). E.g., $ ./src/nix-env/nix-env -qa --description gcc gcc-4.0.2 GNU Compiler Collection, 4.0.x (cross-compiler for sparc-linux) gcc-4.0.2 GNU Compiler Collection, 4.0.x (cross-compiler for mips-linux) gcc-4.0.2 GNU Compiler Collection, 4.0.x (cross-compiler for arm-linux) gcc-4.0.2 GNU Compiler Collection, 4.0.x
2006-03-10 16:20:42 +00:00
nix-env: Fix parsing of --system https://hydra.nixos.org/build/68827814
2018-02-08 14:25:03 +00:00
# Query the system.
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -qa '*' --system | grepQuiet $system
nix-env: Fix parsing of --system https://hydra.nixos.org/build/68827814
2018-02-08 14:25:03 +00:00
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Install "foo-1.0".
Test ~/.nix-defexpr
2014-02-26 17:33:13 +00:00
nix-env -i foo-1.0
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Query installed: should contain foo-1.0 now (which should be
# executable).
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
test "$(nix-env -q '*' | wc -l)" -eq 1
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -q '*' | grepQuiet foo-1.0
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
test "$($profiles/test/bin/foo)" = "foo-1.0"
Test the -b and -s flags of nix-store -q
2014-02-26 17:40:08 +00:00
# Test nix-env -qc to compare installed against available packages, and vice versa.
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -qc '*' | grepQuiet '< 2.0'
nix-env -qac '*' | grepQuiet '> 1.0'
Test the -b and -s flags of nix-store -q
2014-02-26 17:40:08 +00:00
# Test the -b flag to filter out source-only packages.
[ "$(nix-env -qab | wc -l)" -eq 1 ]
# Test the -s flag to get package status.
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -qas | grepQuiet 'IP- foo-1.0'
nix-env -qas | grepQuiet -- '--- bar-0.1'
Test the -b and -s flags of nix-store -q
2014-02-26 17:40:08 +00:00
Add a test for ‘nix-env --set-flag active ...’
2012-12-04 13:30:34 +00:00
# Disable foo.
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
nix-env --set-flag active false foo
Fix tests So all these years I was totally deluded about the meaning of "set -e". You might think that it causes statements like "false && true" or "! true" to fail, but it doesn't...
2014-08-21 19:50:19 +00:00
(! [ -e "$profiles/test/bin/foo" ])
Add a test for ‘nix-env --set-flag active ...’
2012-12-04 13:30:34 +00:00
# Enable foo.
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
nix-env --set-flag active true foo
Add a test for ‘nix-env --set-flag active ...’
2012-12-04 13:30:34 +00:00
[ -e "$profiles/test/bin/foo" ]
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Store the path of foo-1.0.
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
outPath10_=$(nix-env -q --out-path --no-name '*' | grep foo-1.0)
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
echo "foo-1.0 = $outPath10"
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
[ "$outPath10" = "$outPath10_" ]
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Install "foo-2.0pre1": should remove foo-1.0.
Test ~/.nix-defexpr
2014-02-26 17:33:13 +00:00
nix-env -i foo-2.0pre1
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Query installed: should contain foo-2.0pre1 now.
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
test "$(nix-env -q '*' | wc -l)" -eq 1
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -q '*' | grepQuiet foo-2.0pre1
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
test "$($profiles/test/bin/foo)" = "foo-2.0pre1"
# Upgrade "foo": should install foo-2.0.
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
NIX_PATH=nixpkgs=./user-envs.nix:${NIX_PATH-} nix-env -f '<nixpkgs>' -u foo
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Query installed: should contain foo-2.0 now.
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
test "$(nix-env -q '*' | wc -l)" -eq 1
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -q '*' | grepQuiet foo-2.0
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
test "$($profiles/test/bin/foo)" = "foo-2.0"
# Store the path of foo-2.0.
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
outPath20=$(nix-env -q --out-path --no-name '*' | grep foo-2.0)
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
test -n "$outPath20"
# Install bar-0.1, uninstall foo.
Test ~/.nix-defexpr
2014-02-26 17:33:13 +00:00
nix-env -i bar-0.1
nix-env -e foo
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Query installed: should only contain bar-0.1 now.
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
if nix-env -q '*' | grepQuiet foo; then false; fi
nix-env -q '*' | grepQuiet bar
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Rollback: should bring "foo" back.
Test nix-env --switch-generation
2014-02-26 17:45:26 +00:00
oldGen="$(nix-store -q --resolve $profiles/test)"
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
nix-env --rollback
Test nix-env --switch-generation
2014-02-26 17:45:26 +00:00
[ "$(nix-store -q --resolve $profiles/test)" != "$oldGen" ]
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -q '*' | grepQuiet foo-2.0
nix-env -q '*' | grepQuiet bar
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Rollback again: should remove "bar".
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
nix-env --rollback
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -q '*' | grepQuiet foo-2.0
if nix-env -q '*' | grepQuiet bar; then false; fi
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Count generations.
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
nix-env --list-generations
test "$(nix-env --list-generations | wc -l)" -eq 7
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
Mis-read Eelko's request to not make this an option: now, let's not make it an option. :)
2015-05-20 15:29:52 +00:00
# Doing the same operation twice results in the same generation, which triggers
# "lazy" behaviour and does not create a new symlink.
Implement alternative to lazy generations: * only the last generation can be lazy * depend on the '--lazy-generation' flag to be set
2015-05-19 18:03:36 +00:00
Mis-read Eelko's request to not make this an option: now, let's not make it an option. :)
2015-05-20 15:29:52 +00:00
nix-env -i foo
Enable lazy/sparse allocation of generation symlinks: avoid creating new generations if a generation already exists. Alternatively or additionally I propose a mode where only the *last* generation will be sparse.
2015-05-18 06:38:49 +00:00
nix-env -i foo
# Count generations.
nix-env --list-generations
Implement alternative to lazy generations: * only the last generation can be lazy * depend on the '--lazy-generation' flag to be set
2015-05-19 18:03:36 +00:00
test "$(nix-env --list-generations | wc -l)" -eq 8
Test nix-env --switch-generation
2014-02-26 17:45:26 +00:00
# Switch to a specified generation.
nix-env --switch-generation 7
[ "$(nix-store -q --resolve $profiles/test)" = "$oldGen" ]
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Install foo-1.0, now using its store path.
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
nix-env -i "$outPath10"
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -q '*' | grepQuiet foo-1.0
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
nix-store -qR $profiles/test | grep "$outPath10"
nix-store -q --referrers-closure $profiles/test | grep "$(nix-store -q --resolve $profiles/test)"
[ "$(nix-store -q --deriver "$outPath10")" = $drvPath10 ]
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
* nix-env -e: support uninstalling by path, so that one can say $ nix-env -e $(which firefox) or $ nix-env -e /nix/store/nywzlygrkfcgz7dfmhm5xixlx1l0m60v-pan-0.132 * nix-env -i: if an argument contains a slash anywhere, treat it as a path and follow it through symlinks into the Nix store. This allows things like $ nix-build -A firefox $ nix-env -i ./result * nix-env -q/-i/-e: don't complain when the `*' selector doesn't match anything. In particular, `nix-env -q \*' doesn't fail anymore on an empty profile.
2007-11-29 16:18:24 +00:00
# Uninstall foo-1.0, using a symlink to its store path.
ln -sfn $outPath10/bin/foo $TEST_ROOT/symlink
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
nix-env -e $TEST_ROOT/symlink
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
if nix-env -q '*' | grepQuiet foo; then false; fi
nix-store -qR $profiles/test | grepInverse "$outPath10"
* nix-env -e: support uninstalling by path, so that one can say $ nix-env -e $(which firefox) or $ nix-env -e /nix/store/nywzlygrkfcgz7dfmhm5xixlx1l0m60v-pan-0.132 * nix-env -i: if an argument contains a slash anywhere, treat it as a path and follow it through symlinks into the Nix store. This allows things like $ nix-build -A firefox $ nix-env -i ./result * nix-env -q/-i/-e: don't complain when the `*' selector doesn't match anything. In particular, `nix-env -q \*' doesn't fail anymore on an empty profile.
2007-11-29 16:18:24 +00:00
# Install foo-1.0, now using a symlink to its store path.
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
nix-env -i $TEST_ROOT/symlink
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -q '*' | grepQuiet foo
* nix-env -e: support uninstalling by path, so that one can say $ nix-env -e $(which firefox) or $ nix-env -e /nix/store/nywzlygrkfcgz7dfmhm5xixlx1l0m60v-pan-0.132 * nix-env -i: if an argument contains a slash anywhere, treat it as a path and follow it through symlinks into the Nix store. This allows things like $ nix-build -A firefox $ nix-env -i ./result * nix-env -q/-i/-e: don't complain when the `*' selector doesn't match anything. In particular, `nix-env -q \*' doesn't fail anymore on an empty profile.
2007-11-29 16:18:24 +00:00
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Delete all old generations.
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
nix-env --delete-generations old
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
# Run the garbage collector. This should get rid of foo-2.0 but not
# foo-1.0.
* Refactoring: remove unnecessary variables from the tests.
2011-10-10 21:32:34 +00:00
nix-collect-garbage
* Tests for nix-env, finally!
2006-02-08 14:32:06 +00:00
test -e "$outPath10"
Fix tests So all these years I was totally deluded about the meaning of "set -e". You might think that it causes statements like "false && true" or "! true" to fail, but it doesn't...
2014-08-21 19:50:19 +00:00
(! [ -e "$outPath20" ])
* Regression test for NIX-31.
2006-02-17 17:03:19 +00:00
# Uninstall everything
Test ~/.nix-defexpr
2014-02-26 17:33:13 +00:00
nix-env -e '*'
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
test "$(nix-env -q '*' | wc -l)" -eq 0
* Regression test for NIX-31.
2006-02-17 17:03:19 +00:00
# Installing "foo" should only install the newest foo.
Test ~/.nix-defexpr
2014-02-26 17:33:13 +00:00
nix-env -i foo
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
test "$(nix-env -q '*' | grep foo- | wc -l)" -eq 1
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -q '*' | grepQuiet foo-2.0
* Regression test for NIX-31.
2006-02-17 17:03:19 +00:00
* And another test.
2006-02-17 17:05:34 +00:00
# On the other hand, this should install both (and should fail due to
# a collision).
Test ~/.nix-defexpr
2014-02-26 17:33:13 +00:00
nix-env -e '*'
Fix tests So all these years I was totally deluded about the meaning of "set -e". You might think that it causes statements like "false && true" or "! true" to fail, but it doesn't...
2014-08-21 19:50:19 +00:00
(! nix-env -i foo-1.0 foo-2.0)
* And another test.
2006-02-17 17:05:34 +00:00
* Regression test for NIX-31.
2006-02-17 17:03:19 +00:00
# Installing "*" should install one foo and one bar.
Test ~/.nix-defexpr
2014-02-26 17:33:13 +00:00
nix-env -e '*'
nix-env -i '*'
Test nix-store --switch-profile and more daemon actions
2014-02-26 17:28:55 +00:00
test "$(nix-env -q '*' | wc -l)" -eq 2
Harden tests' bash Use `set -u` and `set -o pipefail` to catch accidental mistakes and failures more strongly. - `set -u` catches the use of undefined variables - `set -o pipefail` catches failures (like `set -e`) earlier in the pipeline. This makes the tests a bit more robust. It is nice to read code not worrying about these spurious success paths (via uncaught) errors undermining the tests. Indeed, I caught some bugs doing this. There are a few tests where we run a command that should fail, and then search its output to make sure the failure message is one that we expect. Before, since the `grep` was the last command in the pipeline the exit code of those failing programs was silently ignored. Now with `set -o pipefail` it won't be, and we have to do something so the expected failure doesn't accidentally fail the test. To do that we use `expect` and a new `expectStderr` to check for the exact failing exit code. See the comments on each for why. `grep -q` is replaced with `grepQuiet`, see the comments on that function for why. `grep -v` when we just want the exit code is replaced with `grepInverse, see the comments on that function for why. `grep -q -v` together is, surprise surprise, replaced with `grepQuietInverse`, which is both combined. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2021-12-09 15:26:46 +00:00
nix-env -q '*' | grepQuiet foo-2.0
nix-env -q '*' | grepQuiet bar-0.1.1
Test priorities
2012-12-04 13:47:50 +00:00
# Test priorities: foo-0.1 has a lower priority than foo-1.0, so it
# should be possible to install both without a collision. Also test
Revert "Get rid of unicode quotes (#1140)" This reverts commit f78126bfd6b6c8477fcdbc09b2f98772dbe9a1e7. There really is no need for such a massive change...
2016-11-25 23:37:43 +00:00
# ‘--set-flag priority’ to manually override the declared priorities.
Test ~/.nix-defexpr
2014-02-26 17:33:13 +00:00
nix-env -e '*'
nix-env -i foo-0.1 foo-1.0
Test priorities
2012-12-04 13:47:50 +00:00
[ "$($profiles/test/bin/foo)" = "foo-1.0" ]
Test ~/.nix-defexpr
2014-02-26 17:33:13 +00:00
nix-env --set-flag priority 1 foo-0.1
Test priorities
2012-12-04 13:47:50 +00:00
[ "$($profiles/test/bin/foo)" = "foo-0.1" ]
Test nix-env --set
2014-02-26 17:42:19 +00:00
# Test nix-env --set.
nix-env --set $outPath10
[ "$(nix-store -q --resolve $profiles/test)" = $outPath10 ]
nix-env --set $drvPath10
[ "$(nix-store -q --resolve $profiles/test)" = $outPath10 ]
Handle the case where a parent of ~/.nix-defexpr is a symlink Fixes https://github.com/DeterminateSystems/nix-installer/issues/912 and probably #10247.
2024-04-03 13:28:13 +00:00
# Test the case where $HOME contains a symlink.
mkdir -p $TEST_ROOT/real-home/alice/.nix-defexpr/channels
ln -sfn $TEST_ROOT/real-home $TEST_ROOT/home
ln -sfn $(pwd)/user-envs.nix $TEST_ROOT/home/alice/.nix-defexpr/channels/foo
HOME=$TEST_ROOT/home/alice nix-env -i foo-0.1
Reference in New Issue Copy Permalink