Eelco Dolstra
28b62dd3e0
Merge remote-tracking branch 'origin/master' into lazy-trees
2022-09-28 14:13:44 +02:00
Eelco Dolstra
dfc3a9afc3
Merge pull request #7043 from edolstra/installer-test
...
Add an installer test
2022-09-26 17:34:23 +02:00
Eelco Dolstra
71e364c9c7
Quote URLs
2022-09-26 16:57:06 +02:00
Eelco Dolstra
eceaf1997c
Remove FIXME
2022-09-26 16:54:31 +02:00
John Ericson
a2a8cb10ac
Dodge "trusted" vs "trustworthy" by being explicit
...
Hopefully this is best!
2022-09-22 14:37:52 -04:00
John Ericson
752f967c0f
"valid signature" -> "trustworthy signature"
...
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-22 10:49:31 -04:00
Eelco Dolstra
0d4bf9c4d8
Fix evaluation
2022-09-15 15:56:46 +02:00
Eelco Dolstra
3dd313a7c2
Add RHEL 9
2022-09-15 15:50:52 +02:00
Eelco Dolstra
ba04b5b1d7
Disable Ubuntu 14.04
2022-09-15 14:51:44 +02:00
Eelco Dolstra
a96ad2ab25
Add RHEL 7/8
2022-09-15 14:51:10 +02:00
Eelco Dolstra
503f31e2a0
Use libvirt image
2022-09-15 13:28:03 +02:00
Eelco Dolstra
ef714aa8a5
Remove pre-release Ubuntu 22.10
2022-09-15 13:25:26 +02:00
Eelco Dolstra
5c8cdb9b60
Add Ubuntu 22.04 LTS
2022-09-15 13:24:17 +02:00
Eelco Dolstra
29aaec1e59
Make cross product of images and tests
2022-09-15 13:15:26 +02:00
Eelco Dolstra
fe958a682d
Test building
2022-09-15 11:42:10 +02:00
Eelco Dolstra
cc6e312315
Get Ubuntu 22.10 to work
2022-09-14 19:44:41 +02:00
Eelco Dolstra
906c947ee8
Enable daemon installation test on Fedora
2022-09-14 18:55:45 +02:00
Eelco Dolstra
0a8e666dd6
Add Fedora 36
2022-09-14 18:40:16 +02:00
Eelco Dolstra
fae3b4fe8a
Add an installer test
...
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-14 15:41:11 +02:00
Eelco Dolstra
2a1c63c785
Support flake references in the old CLI
...
Fixes #7026 .
2022-09-13 19:05:05 +02:00
Eelco Dolstra
2d5cfca98b
Fix accessing 'toString path'
2022-09-02 19:30:17 +02:00
Eelco Dolstra
a8b3d777fb
Revert "Merge pull request #6621 from Kha/nested-follows"
...
This reverts commit c530cda3454adcdff5c1
2022-09-01 15:26:19 +02:00
Sebastian Ullrich
6f65c11780
Fix overlapping flake follows
2022-08-28 11:50:25 +02:00
Sebastian Ullrich
2b9d381301
Fix nested flake input overrides
2022-08-28 11:47:25 +02:00
Eelco Dolstra
795b21f0da
Merge remote-tracking branch 'origin/master' into lazy-trees
2022-08-17 12:20:35 +02:00
Eelco Dolstra
81e42e0d3f
Fix onError
2022-08-17 11:36:58 +02:00
Eelco Dolstra
a218dd80d6
Support locking path inputs
2022-08-16 16:05:43 +02:00
Eelco Dolstra
2e0d63caf6
Add InputAccessor::fetchToStore()
2022-08-11 20:03:22 +02:00
Félix Baylac-Jacqué
b47b6a418d
tests/check.sh: add nix3-build check test
2022-08-03 12:17:13 +02:00
Eelco Dolstra
55c63c9b89
Remove InputScheme::fetchToStore()
...
InputSchemes now only have a getAccessor(). They could be implemented
internally by fetching the input to the store, but in that case they
will just return a FSInputAccessor.
2022-08-01 15:44:40 +02:00
Eelco Dolstra
360a1284db
Fix onError
2022-07-27 16:41:26 +02:00
Eelco Dolstra
022390af5a
Merge remote-tracking branch 'origin/master' into lazy-trees
2022-07-22 15:27:40 +02:00
Théophane Hufschmitt
fbd0a6c6e2
Merge pull request #6784 from tweag/completion-test
...
Add some tests for the CLI completion
2022-07-18 20:32:14 +02:00
Eelco Dolstra
2532fee157
On test failures, print a bash stack trace
...
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-14 15:07:19 +02:00
Eelco Dolstra
7d5e209f23
Merge remote-tracking branch 'origin/master' into lazy-trees
2022-07-14 15:05:44 +02:00
Eelco Dolstra
b15c4fdbde
Split off 'nix flake check' tests
2022-07-13 21:01:16 +02:00
Eelco Dolstra
752158a8ef
Move flake-searching.sh and make it less dependent on git
2022-07-13 20:55:17 +02:00
Eelco Dolstra
6ba45f81a8
Move flake-local-settings.sh
2022-07-13 20:51:28 +02:00
Eelco Dolstra
7abcafcfea
Move the 'nix bundle' tests
...
Note: these were previously not actually called.
2022-07-13 20:49:07 +02:00
Eelco Dolstra
d16f1070f4
Split off following paths tests
2022-07-13 20:46:22 +02:00
Eelco Dolstra
a094259d35
Split off 'nix flake init' tests
2022-07-13 20:37:40 +02:00
Eelco Dolstra
f011c269c9
Split off the circular flake import tests
2022-07-13 20:37:32 +02:00
Eelco Dolstra
c591efafd3
Split off the Mercurial flake tests
2022-07-13 15:06:57 +02:00
Eelco Dolstra
420957e149
Move flakes tests to a subdirectory
2022-07-13 15:06:54 +02:00
Eelco Dolstra
e1153069bd
Merge pull request #6797 from edolstra/overrides-check
...
Simplify the check for overrides on non-existent inputs
2022-07-13 14:45:07 +02:00
Eelco Dolstra
19190c2346
tests/flakes.sh: Make sure flake7 is clean
...
Cherry-picked from the lazy-trees branch, where we no longer write a
lock file if any of the inputs is dirty.
2022-07-13 13:46:33 +02:00
Eelco Dolstra
12df8885cc
Simplify the check for overrides on non-existent inputs
2022-07-13 13:40:40 +02:00
Eelco Dolstra
53b7407041
Simplify the check for overrides on non-existent inputs
2022-07-13 13:39:06 +02:00
Eelco Dolstra
c5b84e1a16
Fix test
2022-07-13 13:17:10 +02:00
Eelco Dolstra
934f317250
Merge remote-tracking branch 'origin/master' into lazy-trees
2022-07-13 12:50:03 +02:00
