| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recentry the "stable" attribute in the ZFS NixOS test has been
renamed[1] to "series_2_2", so we now get an evaluation error because of
the missing "stable" attribute.
Quoting the commit in question:
> zfs_2_2: Rename from zfsStable
>
> The `zfs` alias already has equivalent semantics. Instead, make this
> like zfs_2_1 so folks who want to pin a specific release series can do
> so easily and clearly to have more control over when more substantial
> updates occur.
>
> Rename all tests to match the pkg attr they are testing.
To fix this, I not only renamed the attribute on our side but also added
the series_2_1 attribute to our heavily outdated core/tests.nix module.
[1]: https://github.com/NixOS/nixpkgs/commit/dcff4f831836e249db5e808aeac
Signed-off-by: aszlig <aszlig@nix.build>
Reported-by: @devhell
|
|
|
|
|
|
| |
We could of course introspect pkgs.nixosTests to find out which tests
are actually available, but this would probably make evaluation even
more expensive.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Unfortunately the version the current default/LTS kernel was never
updated in nixos/tests/wireguard ever since the introduction of the
multi version test feature. https://github.com/NixOS/nixpkgs/pull/338632
will tie it to the default version again after which we can probably
reintroduce a logic similar to this.
Testing the 5.4 version is a bit pointless at the moment. Everyone in
vuizvui seems to be using either the current default version of
linux (6.6) or the latest version, so the latest kernel version is
always “closer” than 5.4.
|
|
|
|
|
|
|
|
|
|
| |
Fixes the following eval error:
error: The option `services.mxisd' can no longer be used since it's
been removed. The mxisd module has been removed as both mxisd and
ma1sd got removed.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
When fixing evaluation for supportedFilesystems in
21fdf5e0407d11524dbc0c42743358d9b973943c, I forgot about another change
related to ZFS options, which leads to the following evaluation error:
The option `boot.zfs.enableUnstable' can no longer be used since it's
been removed. Instead set `boot.zfs.package = pkgs.zfs_unstable;`
Signed-off-by: aszlig <aszlig@nix.build>
Reported-by: https://github.com/devhell
|
|
|
|
|
|
|
|
|
| |
The option boot.supportedFilesystems is now[1] an attribute set instead
of a list, so we need to fix all checks.
[1]: https://github.com/NixOS/nixpkgs/commit/258b935d705be03e939b8205215
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
| |
This fixes the following evaluation error:
error: The option `krb5.kerberos' can no longer be used since it's
been removed. The option `krb5.kerberos' has been moved to
`security.krb5.package'.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
| |
Removed due to a lack of maintenance:
http://github.com/nixos/nixpkgs/commit/022ee4d701878c185785ce72dd436639dd687199
The ELK NixOS test continues to exist.
|
|
|
|
|
|
|
|
|
|
| |
The module options have been restructured in a way that the attribute
set for defining the actual sites is now in a dedicated "sites" option
instead of eg. services.mediawiki directly, so the checks of whether we
should include this for testing always return true since
services.mediawiki is *always* a non-empty attribute set.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
`grub.version` was removed in [1], together with `grub1` in [2].
[1]: https://github.com/NixOS/nixpkgs/commit/30bea8d82d9e9ffa3093106af4527cbfc0663150
[2]: https://github.com/NixOS/nixpkgs/commit/6db74508276ae2c3c48cfea0a7022d01ca273264
|
|
|
|
|
| |
This was removed from nixpkgs due to lack of downstream maintainer.
Also, see https://github.com/NixOS/nixpkgs/pull/225285
|
|
|
|
| |
This was dropped in https://github.com/NixOS/nixpkgs/pull/221469
|
|
|
|
|
|
| |
This was renamed upstream [1].
[1]: https://github.com/NixOS/nixpkgs/pull/198637
|
|
|
|
|
|
|
|
| |
Ref. https://github.com/NixOS/nixpkgs/commit/0977227b8622daccb5a8435d3d4216eedf845973
Evaluating the vuizvui Hydra seemingly hit an infinite loop involving
the rename warning for this change, so hopefully adapting to it makes it
possible to evaluate it again.
|
|
|
|
|
|
|
|
| |
The package has been removed and we're getting the following eval error:
error: 'docker-edge' has been removed, it was an alias for 'docker'
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The options in services.graphite.api and services.graphite.beacon got[1]
removed[2] in nixpkgs because the upstream project doesn't seem to be
maintained anymore.
More information can be found at:
https://github.com/NixOS/nixpkgs/pull/180950
[1]: https://github.com/NixOS/nixpkgs/commit/1f18d441063208968f38bed0fe5
[2]: https://github.com/NixOS/nixpkgs/commit/ada1d87767b8826ea6233952279
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
Since the old URL had all sorts of issues ranging from no HTTP/2 support
to issues with XSRF protection, I decided to move the Hydra instance to
https://hydra.build/ - a domain that I had laying around since years but
didn't use so far.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
This has been renamed a little while ago.
|
|
|
|
| |
This reverts commit 20ee65d79602b6412994dc52907715b274daeebe.
|
|
|
|
|
| |
This must have been a recent change where an assert is now thrown
because some nix.* settings have been regrouped as nix.settings.*
|
|
|
|
|
|
| |
Similar to `moinmoin`, `trac` has been remove upstream[1].
[1]: https://github.com/nixos/nixpkgs/commit/a859ef91f0fef2139742c11eda43ea3d747cbb9e
|
|
|
|
|
|
|
|
|
| |
`moinmoin` has been removed upstream[1]. This fixes eval on vuizvui
again.
[1]: https://github.com/nixos/nixpkgs/commit/5dd90167cea70fe60bebf1ef1fda7e474449b177
The service has been removed from upstream. This fixes
|
| |
|
|
|
|
| |
This makes it usable outside of the module; should be a pure refactor.
|
|
|
|
|
| |
I want to use the mkWrapper function outside of the vuizvui module,
and this error message would be confusing to have.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The varios subservices of Hadoop used "enabled" instead of the common
convention "enable" for their option names, eg:
services.hadoop.hdfs.datanode.enabled
This has been fixed in nixpkgs[1], so we need to do this on our end as
well to avoid an evaluation error.
[1]: https://github.com/NixOS/nixpkgs/commit/c3d147f507e81455ae467f8aa589972af3449f77
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes the following eval error:
The option `services.paperless' can no longer be used since it's been
removed. The paperless module has been removed as the upstream project
died.
Users should migrate to the paperless-ng module (services.paperless-ng).
More information can be found in the NixOS 21.11 release notes.
We don't use paperless in any machines but since we're testing for NixOS
module option definitions, we're running into the eval error above.
Switching to paperless-ng should get rid of them.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far, we have passed self instead of super to our custom package set,
but this makes it very hard when overriding other packages and refering
to one of these packages in Vuizvui.
To fix this, I not only used mkBefore to make sure that the overlay
comes before every other overlay but also using super makes sure that
whenever we do overrides in Vuizvui, the package *before* the current
overlay is selected instead of possibly running into an infinite
recursion.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
This makes it hard to do static analysis on the code and it's really not
needed here, so let's use lib.X directly.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
| |
A few things have changed since the recent NixOS 21.05 release. Mostly
naming stuff, so nothing dramatic.
|
|
|
|
|
|
|
| |
quagga has been removed upstream as it is unmaintained:
https://github.com/nixos/nixpkgs/commit/40945d399d0ff05e24891a989f5fe48a6e4d316a
Fixes eval of all vuizvui machines.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The kernel-lts and kernel-latest tests seem to have been removed (not
sure when exactly, didn't blame). Instead we can use
nixosTests.kernel-generic."linux_${major}_${minor}". This allows us to
easily check for tests for arbitrary kernel versions as well.
However there is currently a bug that these are returned as functions
instead of derivations at the moment which will hopefully be fixed by my
upstream PR soon. Until that happens we check if the test is a
derivation or not with lib.isDerivation.
cc @aszlig for comments / further improvements. Main intention right now
is to fix eval in a future proof way.
|
|
|
|
|
|
|
|
| |
Since we now distribute the programs.sqlite database with the vuizvui
channel, we can make use of it in programs.command-not-found. We change
the default path used to use the nixpkgs sub directory of the vuizvui
channel (by default it expects a channel named nixos containing the
database).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test is not essential for running any real NixOS machines and the
tests just checks whether the runInMachine function for building
derivations inside a VM works.
I was very much reluctant to just remove this test before I actually
fixed the issue upstream because this would mean that it's highly likely
that I'm never going to do it.
However, since all the channels on our side are currently blocking on
this test, which isn't relevant either, I'm going to risk possibly never
fixing runInMachine upstream since I'd have removed that test anyway for
the aforementioned reason.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The upstream Hydra channels are based on the "tested" job in
release-combined.nix, which already contain a bunch of tests that must
succeed for the channel to advance.
Since evaluation time has skyrocketed for us within the last few months,
we now even don't get *any* evaluation since a while since we hit a
timeout of 10 hours.
I have no idea which changes resulted in this spike of evaluation time
but right now I'm too busy with other things to do a proper
investigation.
To hopefully mitigate this, I decided to base our vuizvui jobset on the
"nixos-unstable" channel and we now only run *additional* tests not
already tested by the upstream channel.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was one of the places where types.loaOf was still in place and it
got removed a while[1] ago and this in turn causes evaluation to fail
for quite a few machines:
The option value `boot.initrd.luks.devices' in `...' is not of type
`attribute set of submodules'.
I've not only changed all the machines to use attribute sets but also
fixed the check in core/tests.nix, because comparing against a list when
the actual type is an attribute set will result in all the LUKS tests to
be part of *all* channels, no matter whether you're actually using LUKS.
[1]: https://github.com/NixOS/nixpkgs/commit/20d491a317d9956ddca80913f07
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
Cc: @sternenseemann
|
|
|
|
|
|
|
| |
This has also been removed [1] upstream and therefore needs to be
removed here.
[1]: https://github.com/NixOS/nixpkgs/commit/b2f3bbd3fb958601a7357e39d66f226e065d76c1
|
|
|
|
|
|
|
| |
This package, the module and its test have been removed [1], so to
unbreak Hydra we need to remove it as well.
[1]: https://github.com/NixOS/nixpkgs/commit/aebf9a4709215c230e5841d60e2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I even mentioned the full names of the test attributes in
bc4203d221c87a0622d089aaa61884f86d40fd44:
tests.wireguard.wireguard-basic-linux-5_4
tests.wireguard.wireguard-basic-linux-latest
tests.wireguard.wireguard-generated-linux-5_4
tests.wireguard.wireguard-generated-linux-latest
tests.wireguard.wireguard-namespaces-linux-5_4
tests.wireguard.wireguard-namespaces-linux-latest
tests.wireguard.wireguard-wg-quick-linux-5_4
tests.wireguard.wireguard-wg-quick-linux-latest
So I forgot about the additional "wireguard-" prefix, so Hydra fails to
evaluate again:
in job 'tests.nixos.wireguard.basic-linux-5_4':
evaluation aborted with the following error message: 'cannot find attribute `nixos.wireguard.basic-linux-5_4''
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 89c3cda819da5dc32e4a29ff8f2aad118bde64c7 changed the wireguard
attributes to use nested attributes because it was changed upstream.
However what the commit has missed is that the attributes are not just
plain attributes but come with a kernel version suffix, for example like
this:
tests.wireguard.wireguard-basic-linux-5_4
tests.wireguard.wireguard-basic-linux-latest
tests.wireguard.wireguard-generated-linux-5_4
tests.wireguard.wireguard-generated-linux-latest
tests.wireguard.wireguard-namespaces-linux-5_4
tests.wireguard.wireguard-namespaces-linux-latest
tests.wireguard.wireguard-wg-quick-linux-5_4
tests.wireguard.wireguard-wg-quick-linux-latest
Adding the "-linux-${version}" suffix should fix evaluation.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A few days ago, the wireguard tests were consolidated[1] into a single
attribute with various subattributes, similar to how the virtualbox
tests and many other tests are structured.
I fixed the attributes and also added the wg-quick attribute that was
also introduced in the meantime[2].
This should fix the evaluation errors occuring whenever a channel
contains a machine configuration with wireguard enabled.
[1]: https://github.com/NixOS/nixpkgs/commit/41bd6d2614749d12ce5ded3e991555b56ea6b2dc
[2]: https://github.com/NixOS/nixpkgs/commit/abf60791e2bd274d39e0f18def46795798f9aefd
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
|
|
|
|
|
|
|
|
|
| |
The option has been renamed[1] from just "docker-containers" to
"virtualisation.oci-containers.containers", so our checks no longer
evaluate.
[1]: https://github.com/NixOS/nixpkgs/commit/2f7747526cc80844a506c4aa147
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
With the merge of [1], the `.enable` check for
`config.services.dokuwiki` has been removed.
[1]: https://github.com/NixOS/nixpkgs/pull/83769
|
|
|
|
|
|
|
|
|
|
|
| |
The nesting.clone and nesting.children options were renamed[1] upstream
and they're now contained in one single submodule option, which means
that for our tests we only need to check for config.specialisation
instead of nesting.clone and nesting.children separately.
[1]: https://github.com/NixOS/nixpkgs/commit/ec2d28e3233c4c04fe6afe13e82
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
All of the NixOS options in services.graphite.pager have been removed in
37ffa6ea51f3a3d7e43736b9a5ce3c149dd9d1ee, but since we're using the
"enable" option to check whether we need to run tests, we'll get an eval
error.
Removing the check fixes the evaluation error.
Signed-off-by: aszlig <aszlig@nix.build>
Reported-by: @devhell
|
|
|
|
|
|
|
|
|
| |
Another thing I missed in ffa7a45ba0aa27c926472e23587423bc07a6db53 is
that not only the module got renamed, but its interface has changed as
well and instead of an "enable" option, it's now just an attribute set
of submodules and the service(s) are enabled whenever it's non-empty.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The buildkite-agent module, NixOS test and option got renamed[1] to its
plural form, also supporting multiple agents.
While none of our machines are using the module, we nevertheless need to
fix the module option attribute so that our channels will evaluate.
[1]: https://github.com/NixOS/nixpkgs/commit/f003810989c58746db9ea52f623
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
This test is only really useful in test environments and is imported
only within the QEMU test driver. The NixOS module option is not
available otherwise, which in turn will cause the evaluation to fail.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
Eval error introduced by 0f0e3cef6297d1334a3b1c27bb125490850be84f.
The virtualisation.dockerPreloader attribute doesn't include an "enable"
option, but instead is configured by specifying a list of images.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It has been a while, since we did a full update of all the tests, which
we last did in 3ea85a699a65dbdd4f633d21e70be6859b0f3f8f (April 2018).
Since then, a whole lot of tests were added and a few of them got
removed as well. Since we only did incremential updates whenever
something broke, we didn't have any newer tests.
We should now have conditions of all the tests we have in nixpkgs
master[1] minus a few special ones, which are only related to upstream
image generation (eg. the ec2 test).
[1]: https://github.com/NixOS/nixpkgs/commit/637bb9fa984238f2f7e6235ca11
Signed-off-by: aszlig <aszlig@nix.build>
|