max/nix-super
1
0
Fork 0
mirror of https://github.com/privatevoid-net/nix-super.git synced 2024-12-02 02:16:15 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
nix-super/tests/local.mk

54 lines
1.4 KiB
Makefile
Raw Normal View History

Add support for ‘make installcheck’
2013-11-25 19:47:03 +02:00
nix_tests = \
Make `system-features` a store setting This seems more correct. It also means one can specify the features a store should support with --store and remote-store=..., which is useful. I use this to clean up the build remotes test.
2020-08-12 19:32:36 +03:00
hash.sh lang.sh add.sh simple.sh dependencies.sh \
add NIX_USER_CONF_FILES Motivation: maintain project-level configuration files. Document the whole situation a bit better so that it corresponds to the implementation, and add NIX_USER_CONF_FILES that allows overriding which user files Nix will load during startup.
2020-03-30 16:31:14 +03:00
config.sh \
Add a test for auto-GC This currently fails because we're using POSIX file locks. So when the garbage collector opens and closes its own temproots file, it causes the lock to be released and then deleted by another GC instance.
2019-08-02 18:07:33 +03:00
gc.sh \
gc-concurrent.sh \
gc-auto.sh \
Add support for ‘make installcheck’
2013-11-25 19:47:03 +02:00
referrers.sh user-envs.sh logging.sh nix-build.sh misc.sh fixed.sh \
Remove nix-install-package. Refs #831
2016-08-10 15:20:51 +03:00
gc-runtime.sh check-refs.sh filter-source.sh \
Test relative store paths
2020-07-17 22:50:53 +03:00
local-store.sh remote-store.sh export.sh export-graph.sh \
Remove manifest support Manifests have been superseded by binary caches for years. This also gets rid of nix-pull, nix-generate-patches and bsdiff/bspatch.
2016-04-11 15:16:56 +03:00
timeout.sh secure-drv-outputs.sh nix-channel.sh \
Add support for ‘make installcheck’
2013-11-25 19:47:03 +02:00
multiple-outputs.sh import-derivation.sh fetchurl.sh optimise-store.sh \
Test nix-build with non-local-store --store Just a few small things needed fixing!
2020-12-20 21:55:21 +02:00
binary-cache.sh \
binary-cache-build-remote.sh \
nix-profile.sh repair.sh dump-db.sh case-hack.sh \
Add a mechanism for derivation attributes to reference the derivation's outputs For example, you can now say: configureFlags = "--prefix=${placeholder "out"} --includedir=${placeholder "dev"}"; The strings returned by the ‘placeholder’ builtin are replaced at build time by the actual store paths corresponding to the specified outputs. Previously, you had to work around the inability to self-reference by doing stuff like: preConfigure = '' configureFlags+=" --prefix $out --includedir=$dev" ''; or rely on ad-hoc variable interpolation semantics in Autoconf or Make (e.g. --prefix=\$(out)), which doesn't always work.
2016-08-17 16:12:54 +03:00
check-reqs.sh pass-as-file.sh tarball.sh restricted.sh \
Add a test for diverted stores
2017-05-02 16:09:35 +03:00
placeholders.sh nix-shell.sh \
build-remote: Add a basic test This only runs on Linux because it requires a diverted store (which uses mount/user namespaces).
2017-05-02 16:35:35 +03:00
linux-sandbox.sh \
tests: Add (failing) tests for reported --dry-run issues.
2018-02-07 22:57:44 +02:00
build-dry.sh \
Test remote building with fixed output derivations
2020-08-16 20:38:12 +03:00
build-remote-input-addressed.sh \
Fix max fd calc and add test
2020-08-20 08:08:50 +03:00
ssh-relay.sh \
Rename tests/nar-index -> tests/nar-access
2017-11-14 14:27:40 +02:00
nar-access.sh \
Add fetchMercurial primop E.g. $ nix eval '(fetchMercurial https://www.mercurial-scm.org/repo/hello)' { branch = "default"; outPath = "/nix/store/alvb9y1kfz42bjishqmyy3pphnrh1pfa-source"; rev = "82e55d328c8ca4ee16520036c0aaace03a5beb65"; revCount = 1; shortRev = "82e55d328c8c"; } $ nix eval '(fetchMercurial { url = https://www.mercurial-scm.org/repo/hello; rev = "0a04b987be5ae354b710cefeba0e2d9de7ad41a9"; })' { branch = "default"; outPath = "/nix/store/alvb9y1kfz42bjishqmyy3pphnrh1pfa-source"; rev = "0a04b987be5ae354b710cefeba0e2d9de7ad41a9"; revCount = 0; shortRev = "0a04b987be5a"; } $ nix eval '(fetchMercurial /tmp/unclean-hg-tree)' { branch = "default"; outPath = "/nix/store/cm750cdw1x8wfpm3jq7mz09r30l9r024-source"; rev = "0000000000000000000000000000000000000000"; revCount = 0; shortRev = "000000000000"; }
2017-11-01 17:32:53 +02:00
structured-attrs.sh \
fetchGit: Add a test
2017-11-03 14:33:50 +02:00
fetchGit.sh \
Improve ref validity checking in fetchGit The previous regex was too strict and did not match what git was allowing. It could lead to `fetchGit` not accepting valid branch names, even though they exist in a repository (for example, branch names containing `/`, which are pretty standard, like `release/1.0` branches). The new regex defines what a branch name should **NOT** contain. It takes the definitions from `refs.c` in https://github.com/git/git and `git help check-ref-format` pages. This change also introduces a test for ref name validity checking, which compares the result from Nix with the result of `git check-ref-format --branch`.
2020-05-30 13:29:35 +03:00
fetchGitRefs.sh \
Add test for fetchGit submodule support
2019-10-26 12:09:50 +03:00
fetchGitSubmodules.sh \
Add tests for "nix verify", "nix sign-paths" etc.
2017-11-14 19:24:20 +02:00
fetchMercurial.sh \
Add tests for "nix run"
2017-11-20 19:36:36 +02:00
signing.sh \
rename run to shell in tests
2020-04-30 00:37:21 +03:00
shell.sh \
Add pure evaluation mode In this mode, the following restrictions apply: * The builtins currentTime, currentSystem and storePath throw an error. * $NIX_PATH and -I are ignored. * fetchGit and fetchMercurial require a revision hash. * fetchurl and fetchTarball require a sha256 attribute. * No file system access is allowed outside of the paths returned by fetch{Git,Mercurial,url,Tarball}. Thus 'nix build -f ./foo.nix' is not allowed. Thus, the evaluation result is completely reproducible from the command line arguments. E.g. nix build --pure-eval '( let nix = fetchGit { url = https://github.com/NixOS/nixpkgs.git; rev = "9c927de4b179a6dd210dd88d34bda8af4b575680"; }; nixpkgs = fetchGit { url = https://github.com/NixOS/nixpkgs.git; ref = "release-17.09"; rev = "66b4de79e3841530e6d9c6baf98702aa1f7124e4"; }; in (import (nix + "/release.nix") { inherit nix nixpkgs; }).build.x86_64-linux )' The goal is to enable completely reproducible and traceable evaluation. For example, a NixOS configuration could be fully described by a single Git commit hash. 'nixos-rebuild' would do something like nix build --pure-eval '( (import (fetchGit { url = file:///my-nixos-config; rev = "..."; })).system ') where the Git repository /my-nixos-config would use further fetchGit calls or Git externals to fetch Nixpkgs and whatever other dependencies it has. Either way, the commit hash would uniquely identify the NixOS configuration and allow it to reproduced.
2018-01-16 19:50:38 +02:00
brotli.sh \
Add a test for --check / --repeat
2018-01-19 14:58:28 +02:00
pure-eval.sh \
Add plugins to make Nix more extensible. All plugins in plugin-files will be dlopened, allowing them to statically construct instances of the various Register* types Nix supports.
2018-02-08 18:26:18 +02:00
check.sh \
tests: test nix search behavior
2018-02-26 00:33:17 +02:00
plugins.sh \
Add a test for LegacySSHStore that doesn't require a VM
2018-08-03 21:41:56 +03:00
search.sh \
Add basic flake tests
2019-05-08 00:22:47 +03:00
nix-copy-ssh.sh \
Merge remote-tracking branch 'origin/master' into flakes
2019-08-08 16:49:13 +03:00
post-hook.sh \
Merge remote-tracking branch 'origin/master' into flakes
2019-08-29 17:11:38 +03:00
function-trace.sh \
Merge remote-tracking branch 'origin/master' into flakes
2019-12-04 01:31:09 +02:00
recursive.sh \
Add a test for `nix describe-stores` Doesn't test much, but at least ensures that the command runs properly
2020-09-16 14:52:15 +03:00
describe-stores.sh \
Squashed get CA derivations building
2020-08-07 22:09:26 +03:00
flakes.sh \
Test nix build --json
2020-10-23 16:20:38 +03:00
content-addressed.sh \
Add a test for the copy of CA paths
2020-12-15 10:37:05 +02:00
nix-copy-content-addressed.sh \
Add x86_64 compute levels as additional system types When performing distributed builds of machine learning packages, it would be nice if builders without the required SIMD instructions can be excluded as build nodes. Since x86_64 has accumulated a large number of different instruction set extensions, listing all possible extensions would be unwieldy. AMD, Intel, Red Hat, and SUSE have recently defined four different microarchitecture levels that are now part of the x86-64 psABI supplement and will be used in glibc 2.33: https://gitlab.com/x86-psABIs/x86-64-ABI https://lwn.net/Articles/844831/ This change uses libcpuid to detect CPU features and then uses them to add the supported x86_64 levels to the additional system types. For example on a Ryzen 3700X: $ ~/aps/bin/nix -vv --version | grep "Additional system" Additional system types: i686-linux, x86_64-v1-linux, x86_64-v2-linux, x86_64-v3-linux
2021-02-16 15:32:12 +02:00
build.sh \
compute-levels.sh
Disable parallel.sh test It breaks randomly: http://hydra.nixos.org/build/11152871
2014-05-22 12:38:50 +03:00
# parallel.sh
Comment out fixed content address test
2020-08-17 22:04:54 +03:00
# build-remote-content-addressed-fixed.sh \
Add support for ‘make installcheck’
2013-11-25 19:47:03 +02:00
Update Makefile variable names
2014-02-01 13:23:14 +02:00
install-tests += $(foreach x, $(nix_tests), tests/$(x))
Add support for ‘make installcheck’
2013-11-25 19:47:03 +02:00
Update Makefile variable names
2014-02-01 13:23:14 +02:00
tests-environment = NIX_REMOTE= $(bash) -e
Add support for ‘make installcheck’
2013-11-25 19:47:03 +02:00
Add basic flake tests
2019-05-08 00:22:47 +03:00
clean-files += $(d)/common.sh $(d)/config.nix
Fix the test dependencies Reuse the pre-existing list rather than the one written as part of #3777
2020-07-02 18:15:02 +03:00
test-deps += tests/common.sh tests/config.nix tests/plugins/libplugintest.$(SO_EXT)
Reference in a new issue Copy permalink