aboutsummaryrefslogtreecommitdiff
path: root/tests
AgeCommit message (Collapse)Author
2022-11-29Merge pull request #3600 from NixOS/auto-uid-allocationEelco Dolstra
Automatic UID allocation
2022-11-28Add a setting for enabling cgroupsEelco Dolstra
2022-11-27Fix evaluationEelco Dolstra
2022-11-27Add tests for auto-uid-allocation, uid-range and cgroupsEelco Dolstra
2022-11-23add explanation and testTaeer Bar-Yam
2022-11-16Merge pull request #7134 from yorickvP/disable-dbg-on-completeThéophane Hufschmitt
Temporarily disable the debugger during completion evaluation
2022-11-15Merge pull request #7283 from hercules-ci/issue-6572Théophane Hufschmitt
Fix #6572 `requires non-existent output`
2022-11-14tests: Reproduce #6572Robert Hensing
2022-11-14Test that the result of `readFile` gets ref-scannedThéophane Hufschmitt
2022-11-03tests/impure-derivations.sh: remove unknown experimental feature 'ca-references'Artturin
ca-references was stabilized in d589a6aa8a5d0c9f391400d7e0e209106e89c857
2022-11-03SourceExprCommand: swallow EvalError, add tests for thisYorick van Pelt
Completing things that would error would print an ugly error in the middle of your command line. Avoid printing this error.
2022-10-31Merge pull request #7039 from Mic92/libfetchers-variantThéophane Hufschmitt
libfetchers: avoid api.github.com ratelimit if no github token is set
2022-10-30Also test github flakes when access tokens are providedJörg Thalheim
2022-10-29Update test after api.github.com ratelimit avoidanceSandro Jäckel
2022-10-26Merge pull request #7174 from agbrooks/git-tag-bugEelco Dolstra
Prevent fetchGit from using incorrect cached rev for different refs
2022-10-25Merge pull request #7196 from sternenseemann/reenable-eval-okay-eqThéophane Hufschmitt
tests/lang: re-enable eval-okay-eq.nix tests
2022-10-19tests/lang: re-enable eval-okay-eq.nix testssternenseemann
This is a really old test case (which was originally written before the proper Nix syntax). The tested deep comparison behavior was implemented and reverted soon after due to performance problems, but it has been restored in today's Nix again (thanks to the derivation comparison optimization, presumably).
2022-10-18Add command 'nix store path-from-hash-part'Eelco Dolstra
This exposes the Store::queryPathFromHashPart() interface in the CLI.
2022-10-14Add test for issue 7146Andrew Brooks
2022-10-12Merge pull request #7149 from amjoseph-nixpkgs/pr/intersectAttrs/valuesEelco Dolstra
parseDrvName: remove doc/impl discrepancy, add test covering the gap
2022-10-08tests/lang/eval-okay-versions.nix: add test for previous commitAdam Joseph
This commit adds a test covering the discrepancy between parseDrvName's implementation and documentation (the discrepancy was eliminated in the previous commit).
2022-09-28tests/build-dry: re-enable some testSolene Rapenne
2022-09-26Merge pull request #7043 from edolstra/installer-testEelco Dolstra
Add an installer test
2022-09-26Quote URLsEelco Dolstra
2022-09-26Remove FIXMEEelco Dolstra
2022-09-22Dodge "trusted" vs "trustworthy" by being explicit John Ericson
Hopefully this is best!
2022-09-22"valid signature" -> "trustworthy signature"John Ericson
I just had a colleague get confused by the previous phrase for good reason. "valid" sounds like an *objective* criterion, e.g. and *invalid signature* would be one that would be trusted by no one, e.g. because it misformatted or something. What is actually going is that there might be a signature which is perfectly valid to *someone else*, but not to the user, because they don't trust the corresponding public key. This is a *subjective* criterion, because it depends on the arbitrary and personal choice of which public keys to trust. I therefore think "trustworthy" is a better adjective to use. Whether something is worthy of trust is clearly subjective, and then "trust" within that word nicely evokes `trusted-public-keys` and friends.
2022-09-15Fix evaluationEelco Dolstra
2022-09-15Add RHEL 9Eelco Dolstra
2022-09-15Disable Ubuntu 14.04Eelco Dolstra
2022-09-15Add RHEL 7/8Eelco Dolstra
2022-09-15Use libvirt imageEelco Dolstra
2022-09-15Remove pre-release Ubuntu 22.10Eelco Dolstra
2022-09-15Add Ubuntu 22.04 LTSEelco Dolstra
2022-09-15Make cross product of images and testsEelco Dolstra
2022-09-15Test buildingEelco Dolstra
2022-09-14Get Ubuntu 22.10 to workEelco Dolstra
2022-09-14Enable daemon installation test on FedoraEelco Dolstra
2022-09-14Add Fedora 36Eelco Dolstra
2022-09-14Add an installer testEelco Dolstra
This runs the installer in a QEMU VM. Unlike the old installer test that ran inside a declaratively built RedHat/Debian image, this uses an image from Vagrant.
2022-09-01Revert "Merge pull request #6621 from Kha/nested-follows"Eelco Dolstra
This reverts commit c530cda345377370c52a616d608de88b9d67cd40, reversing changes made to 4adcdff5c1d5f9f135c4ec61d690890443c19e6a.
2022-08-28Fix overlapping flake followsSebastian Ullrich
2022-08-28Fix nested flake input overridesSebastian Ullrich
2022-08-17Fix onErrorEelco Dolstra
2022-08-03tests/check.sh: add nix3-build check testFélix Baylac-Jacqué
2022-07-18Merge pull request #6784 from tweag/completion-testThéophane Hufschmitt
Add some tests for the CLI completion
2022-07-14On test failures, print a bash stack traceEelco Dolstra
This makes it easier to identify what command failed. It looks like: follow-paths.sh: test failed at: main in follow-paths.sh:54
2022-07-13Split off 'nix flake check' testsEelco Dolstra
2022-07-13Move flake-searching.sh and make it less dependent on gitEelco Dolstra
2022-07-13Move flake-local-settings.shEelco Dolstra