max/nix-super
1
0
Fork 0
mirror of https://github.com/privatevoid-net/nix-super.git synced 2024-11-15 18:56:16 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
nix-super/tests/functional/nix-channel.sh

72 lines
2.2 KiB
Bash
Raw Normal View History

Ensure all functional scripts are (a) executable (b) have shebang This is good for shebang, and also good for future build system simplifications
2024-05-28 19:43:04 +03:00
#!/usr/bin/env bash
* Add a test for nix-channel. * Refactor the nix-channel unpacker a bit.
2012-01-03 03:51:38 +02:00
source common.sh
clearProfiles
Test the NAR info cache
2016-05-30 15:53:57 +03:00
rm -f $TEST_HOME/.nix-channels $TEST_HOME/.nix-profile
* Add a test for nix-channel. * Refactor the nix-channel unpacker a bit.
2012-01-03 03:51:38 +02:00
# Test add/list/remove.
nix-channel improvements "nix-channel --add" now accepts a second argument: the channel name. This allows channels to have a nicer name than (say) nixpkgs_unstable. If no name is given, it defaults to the last component of the URL (with "-unstable" or "-stable" removed). Also, channels are now stored in a profile (/nix/var/nix/profiles/per-user/$USER/channels). One advantage of this is that it allows rollbacks (e.g. if "nix-channel --update" gives an undesirable update).
2012-04-14 19:38:52 +03:00
nix-channel --add http://foo/bar xyzzy
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 17:26:46 +02:00
nix-channel --list | grepQuiet http://foo/bar
nix-channel improvements "nix-channel --add" now accepts a second argument: the channel name. This allows channels to have a nicer name than (say) nixpkgs_unstable. If no name is given, it defaults to the last component of the URL (with "-unstable" or "-stable" removed). Also, channels are now stored in a profile (/nix/var/nix/profiles/per-user/$USER/channels). One advantage of this is that it allows rollbacks (e.g. if "nix-channel --update" gives an undesirable update).
2012-04-14 19:38:52 +03:00
nix-channel --remove xyzzy
Test `nix-channel --list-generations` Rough test, but the feature is a fairly trivial addition on top of `nix-profile --list-generations`, so it should be enough
2023-06-02 11:20:54 +03:00
[[ $(nix-channel --list-generations | wc -l) == 1 ]]
* Add a test for nix-channel. * Refactor the nix-channel unpacker a bit.
2012-01-03 03:51:38 +02:00
Test the NAR info cache
2016-05-30 15:53:57 +03:00
[ -e $TEST_HOME/.nix-channels ]
[ "$(cat $TEST_HOME/.nix-channels)" = '' ]
* Add a test for nix-channel. * Refactor the nix-channel unpacker a bit.
2012-01-03 03:51:38 +02:00
A setting to follow XDG Base Directory standard XDG Base Directory is a standard for locations for storing various files. Nix has a few files which seem to fit in the standard, but currently use a custom location directly in the user's ~, polluting it: - ~/.nix-profile - ~/.nix-defexpr - ~/.nix-channels This commit adds a config option (use-xdg-base-directories) to follow the XDG spec and instead use the following locations: - $XDG_STATE_HOME/nix/profile - $XDG_STATE_HOME/nix/defexpr - $XDG_STATE_HOME/nix/channels If $XDG_STATE_HOME is not set, it is assumed to be ~/.local/state. Co-authored-by: Théophane Hufschmitt <7226587+thufschmitt@users.noreply.github.com> Co-authored-by: Tim Fenney <kodekata@gmail.com> Co-authored-by: pasqui23 <pasqui23@users.noreply.github.com> Co-authored-by: Artturin <Artturin@artturin.com> Co-authored-by: John Ericson <Ericson2314@Yahoo.com>
2021-11-17 22:35:21 +02:00
# Test the XDG Base Directories support
export NIX_CONFIG="use-xdg-base-directories = true"
nix-channel --add http://foo/bar xyzzy
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 17:26:46 +02:00
nix-channel --list | grepQuiet http://foo/bar
A setting to follow XDG Base Directory standard XDG Base Directory is a standard for locations for storing various files. Nix has a few files which seem to fit in the standard, but currently use a custom location directly in the user's ~, polluting it: - ~/.nix-profile - ~/.nix-defexpr - ~/.nix-channels This commit adds a config option (use-xdg-base-directories) to follow the XDG spec and instead use the following locations: - $XDG_STATE_HOME/nix/profile - $XDG_STATE_HOME/nix/defexpr - $XDG_STATE_HOME/nix/channels If $XDG_STATE_HOME is not set, it is assumed to be ~/.local/state. Co-authored-by: Théophane Hufschmitt <7226587+thufschmitt@users.noreply.github.com> Co-authored-by: Tim Fenney <kodekata@gmail.com> Co-authored-by: pasqui23 <pasqui23@users.noreply.github.com> Co-authored-by: Artturin <Artturin@artturin.com> Co-authored-by: John Ericson <Ericson2314@Yahoo.com>
2021-11-17 22:35:21 +02:00
nix-channel --remove xyzzy
unset NIX_CONFIG
[ -e $TEST_HOME/.local/state/nix/channels ]
[ "$(cat $TEST_HOME/.local/state/nix/channels)" = '' ]
* Add a test for nix-channel. * Refactor the nix-channel unpacker a bit.
2012-01-03 03:51:38 +02:00
# Create a channel.
rm -rf $TEST_ROOT/foo
mkdir -p $TEST_ROOT/foo
Resolve symlinks in a few more places Fixes #9882.
2024-01-30 16:00:18 +02:00
drvPath=$(nix-instantiate dependencies.nix)
nix copy --to file://$TEST_ROOT/foo?compression="bzip2" $(nix-store -r "$drvPath")
* Add a test for nix-channel. * Refactor the nix-channel unpacker a bit.
2012-01-03 03:51:38 +02:00
rm -rf $TEST_ROOT/nixexprs
mkdir -p $TEST_ROOT/nixexprs
No longer copy functional tests to the build dir This should make `_NIX_TEST_ACCEPT=1` work again, fixing #11369. Progress on #2503
2024-11-01 15:56:50 +02:00
cp "${config_nix}" dependencies.nix dependencies.builder*.sh $TEST_ROOT/nixexprs/
* Add a test for nix-channel. * Refactor the nix-channel unpacker a bit.
2012-01-03 03:51:38 +02:00
ln -s dependencies.nix $TEST_ROOT/nixexprs/default.nix
* FreeBSD tar defaults to the tape device instead of stdout.
2012-01-03 14:18:41 +02:00
(cd $TEST_ROOT && tar cvf - nixexprs) | bzip2 > $TEST_ROOT/foo/nixexprs.tar.bz2
* Add a test for nix-channel. * Refactor the nix-channel unpacker a bit.
2012-01-03 03:51:38 +02:00
# Test the update action.
nix-channel --add file://$TEST_ROOT/foo
nix-channel --update
Test `nix-channel --list-generations` Rough test, but the feature is a fairly trivial addition on top of `nix-profile --list-generations`, so it should be enough
2023-06-02 11:20:54 +03:00
[[ $(nix-channel --list-generations | wc -l) == 2 ]]
* Add a test for nix-channel. * Refactor the nix-channel unpacker a bit.
2012-01-03 03:51:38 +02:00
# Do a query.
nix-env -qa \* --meta --xml --out-path > $TEST_ROOT/meta.xml
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 17:26:46 +02:00
grepQuiet 'meta.*description.*Random test package' $TEST_ROOT/meta.xml
grepQuiet 'item.*attrPath="foo".*name="dependencies-top"' $TEST_ROOT/meta.xml
* Add a test for nix-channel. * Refactor the nix-channel unpacker a bit.
2012-01-03 03:51:38 +02:00
# Do an install.
tests/binary-cache.sh: Improve incomplete closure test Issue #3373.
2020-05-12 14:49:55 +03:00
nix-env -i dependencies-top
nix-env: Create ~/.nix-profile automatically
2019-10-09 20:21:07 +03:00
[ -e $TEST_HOME/.nix-profile/foobar ]
Support tarballs in nix channel URLs
2015-04-20 07:34:29 +03:00
# Test updating from a tarball
Test the update of multiple channels Make sure that `nix-channel --update` won’t accidentaly remove one
2021-12-17 10:14:28 +02:00
nix-channel --add file://$TEST_ROOT/foo/nixexprs.tar.bz2 bar
Support tarballs in nix channel URLs
2015-04-20 07:34:29 +03:00
nix-channel --update
# Do a query.
nix-env -qa \* --meta --xml --out-path > $TEST_ROOT/meta.xml
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 17:26:46 +02:00
grepQuiet 'meta.*description.*Random test package' $TEST_ROOT/meta.xml
grepQuiet 'item.*attrPath="bar".*name="dependencies-top"' $TEST_ROOT/meta.xml
grepQuiet 'item.*attrPath="foo".*name="dependencies-top"' $TEST_ROOT/meta.xml
Support tarballs in nix channel URLs
2015-04-20 07:34:29 +03:00
# Do an install.
tests/binary-cache.sh: Improve incomplete closure test Issue #3373.
2020-05-12 14:49:55 +03:00
nix-env -i dependencies-top
nix-env: Create ~/.nix-profile automatically
2019-10-09 20:21:07 +03:00
[ -e $TEST_HOME/.nix-profile/foobar ]
Support tarballs in nix channel URLs
2015-04-20 07:34:29 +03:00
Resolve symlinks in a few more places Fixes #9882.
2024-01-30 16:00:18 +02:00
# Test evaluation through a channel symlink (#9882).
nix-instantiate '<foo/dependencies.nix>'
Reference in a new issue Copy permalink