| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
The SLIM project is abandoned and their last release was in 2013.
Because of this it poses a security risk to systems, no one is working
on it or picked up maintenance. It also lacks compatibility with systemd
and logind sessions. For users, there liikely isn't anything like slim
that's as lightweight in terms of dependencies.
|
| |
|
|
| |
Make sure the fonts.enableDefaultFonts option works.
|
| |
|
|
| |
This is pretty much identical to the xfce test we currently have.
|
| | |
|
| | |
|
| |
|
|
|
| |
This has been tested in the Pantheon test
for a year now and it does fine on hydra.
|
| |
|
|
|
| |
We should be ensuring that this session functions
as well because it's default.
|
| | |
|
| |
|
|
|
|
|
| |
IPv6 container support broke a while ago and we didn't notice it. Making
them part of the (small) release test set should fix that. At this point
in time they should be granted the same amount of importance as the
legacy IP tests.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is because it will not eval properly with `hydra-eval-jobs`.
```
$ ...hydra/result/bin/hydra-eval-jobs \
--arg nixpkgs '{ outPath = ./.; revCount = 123; shortRev = "4567"; }' \
-I "$PWD" \
nixos/release-combined.nix
```
It fails with:
```
Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
```
|
| |
|
|
| |
This will block channel advancing, even if it is limited support.
|
| |
|
|
| |
And filters out JDK which can't be built on aarch64-linux.
|
| |
|
|
|
|
|
| |
This was previously removed in 74c4e30842657d09ec1cf000af89f95df27c6632.
This will allow hydra to build iso and sd images for aarch64-linux, and
share a common channel with the x86-based platforms.
|
| |
|
|
|
| |
Temporary fix for #41538; non-deterministic failures
blocked the release channel.
|
| |
|
|
| |
bug introduced by f8d047da50dbc7d012a8d322b4d5e5a0b639733c
|
| |
|
|
| |
... with release-small.nix
Tests for small channel should be a subset of tests for full channel.
|
| |
|
|
|
| |
This reverts commit 1d0625499854b583c57267a744111ba8a1d0cfaf.
We now get a build and maybe have a workaround #39570; /cc #39476.
|
| |
|
|
|
|
|
| |
The chromium package will frequently time out . Note that this is unrelated to the test but a side effect because the test depends on chromium.
https://hydra.nixos.org/job/nixos/trunk-combined/nixos.tests.chromium.x86_64-linux
See also #39476
|
| |
|
|
| |
... in supportedSystems
|
| |
|
|
|
|
|
|
|
|
|
| |
Currently, when building NixOS from a git clone, Nix has to copy
the entire repo at >1GB into the store by default. That is not
necessary and causes a dumping large path message.
If you need the old behaviour for some reason, you will have to
specify it by passing the path to your repo explicitly as the
nixpkgs argument like this:
--arg nixpkgs '{outPath = ./.; revCount = 56789; shortRev = "gfedcba"; }'
|
| |
|
|
|
|
|
| |
In practice it already is since the channel update script barfs out if
the job fails:
https://github.com/NixOS/nixos-channel-scripts/blob/9f96e1e25d197de46d5dbe3c4f81b8d57b9c9821/mirror-nixos-branch.pl#L132
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The existing callSubTests seems to already have special-cased code to
allow enabling subtests on a single specific system by looking at the
`system` attribute in the test arguments. Replace it with a new version
similar to the callTestOnTheseSystems because:
- It's consistent with the existing functions for creating
system-specific tests (though admittedly, the callSubTests special
case for `system` predates them)
- This approach allows limiting to multiple system types, the previous
one inherently allows only one system type.
- This also fixes the problem that if you pass in e.g.
supportedSystems = [ "aarch64-linux" ], you end up with a
tests.chromium job that silently runs on x86_64-linux.
- Finally, this causes renames of the jobs like:
tests.chromium -> tests.chromium.x86_64-linux to be consistent with
the rest of the tests.
|
| |
|
|
|
|
|
|
|
|
|
| |
Currently, even if you pass supportedSystems = [ "aarch64-linux" ] you
end up with e.g. `nixos.tests.docker` which actually silently runs on
x86_64-linux. Using the new callTestOnTheseSystems fixes that.
As a side-effect, this also causes a rename of
`nixos.tests.docker` -> `nixos.tests.docker.x86_64-linux`, which is IMHO
a good thing since it's makes them consistent with the rest of the
tests.
|
| |\
| |
| | |
nixos/system: make switch-to-configuration script pure
|
| | | |
|
| |\ \
| | |
| | | |
nixos/tests: add a test for config.users.mutableUsers.
|
| | |/ |
|
| |/ |
|
| |
|
|
|
|
| |
Lately failing i686 tests like firefox have been blocking channel
releases. We're still building the tests for systems with limited
support but won't delay a channel release if they fail.
|
| |
|
|
|
|
| |
Arguably, breaking linux-latest should not block a release. Also, booting
the kernel + basic sanity checking is implicitly exercised by every other
vm test.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
- sysctl is new and never succeeded on i686-linux
> cannot stat /proc/sys/net/core/bpf_jit_enable: No such file or directory
- testing plasma5 on i686 would defeat part of the reason why we ended
supporting i686 (lots of stuff built on Hydra)
|
| | |
|
| | |
|
| |\
| |
| | |
More basic system tests
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
docker: Package in module, tests
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
Add XMonad test
|
| | |/ |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
| |
Seems to be working fine, based on the history:
https://hydra.nixos.org/job/nixos/trunk-combined/nixos.tests.installer.simpleUefiGummiboot.i686-linux/all
https://hydra.nixos.org/job/nixos/trunk-combined/nixos.tests.installer.simpleUefiGummiboot.x86_64-linux/all
|