about summary refs log tree commit diff
path: root/nixos/tests
Commit message (Collapse)AuthorAge
...
* gnome3_20: Add GNOME 3.20 package setDamien Cassou2016-06-06
|
* nixos kde5: improve testJoel Moberg2016-06-01
| | | | | | IceWM is not part of KDE 5 and is now no longer part of the test. KDE 5 applications: Dolphin, System Monitor, and System Settings are started in this test.
* Rename boot.loader.gummiboot.enable -> boot.loader.systemd-boot.enableEelco Dolstra2016-06-01
|
* Use systemd-boot instead of gummibootEelco Dolstra2016-05-31
| | | | Gummiboot is part of systemd now so we may as well use it.
* nixos/tests/vbox: Fix invocation of dbusaszlig2016-05-26
| | | | | | | | | | | | | | VBoxService needs dbus in order to work properly, which failed to start up so far, because it was searching in /run/current-system/sw for its configuration files. We now no longer run with the --system flag but specify the configuration file directly instead. This fixes at least the "simple-gui" test and probably the others as well, which I haven't tested yet. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* nixos/tests/vbox: Replace waitForWindow with xpropaszlig2016-05-26
| | | | | | | | | | | We can't use waitForWindow here because it runs xwininfo as user root, who in turn is not authorized to connect to the X server running as alice. So instead, we use xprop from user alice which should fix waiting for the VirtualBox manager window. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* nixos/tests/vbox: Start X server with user "alice"aszlig2016-05-26
| | | | | | | | | | | | | | | | The VirtualBox tests so far ran the X server as root instead of user "alice" and it did work, because we had access control turned off by default. Fortunately, it was changed in 1541fa351b4d664c51dddaeaa67ee0652892f405. As a side effect, it caused all the VirtualBox tests to fail because they now can't connect to the X server, which is a good thing because it's a bug of the VirtualBox tests. So to fix it, let's just start the X server as user alice. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* nixos/tests/installer.nix: nixos-generate-config detects LUKS since a7baec7obadz2016-05-26
| | | | Fixes nix-build '<nixos/release.nix>' -A tests.installer.luksroot.x86_64-linux
* boot.initrd.luks.devices: Change into an attribute setEelco Dolstra2016-05-25
| | | | | | | | | | | | | | | This allows setting options for the same LUKS device in different modules. For example, the auto-generated hardware-configuration.nix can contain boot.initrd.luks.devices.crypted.device = "/dev/disk/..."; while configuration.nix can add boot.initrd.luks.devices.crypted.allowDiscards = true; Also updated the examples/docs to use /disk/disk/by-uuid instead of /dev/sda, since we shouldn't promote the use of the latter.
* nixos/tests/boot.nix: Remove empty moduleEelco Dolstra2016-05-25
|
* nixos.tests.swraid: Drop mdadm -WEelco Dolstra2016-05-24
| | | | | | | | | This command is racy because it will return a non-zero exit code if the array is already clean. This caused numerous random failures. It should be unnecessary anyway. (Maybe in the past we needed this because of #15226.) http://hydra.nixos.org/job/nixos/release-16.03/nixos.tests.installer.swraid.i686-linux
* rename iElectric to domenkozar to match GitHubDomen Kožar2016-05-17
|
* nixos/tests/boot-stage1: Add myself to maintainersaszlig2016-05-06
| | | | | | | | | | | | As @edolstra pointed out that the kernel module might be painful to maintain. I strongly disagree because it's only a small module and it's good to have such a canary in the tests no matter how the bootup process looks like, so I'm going the masochistic route and try to maintain it. If it *really* becomes too much maintenance burden, we can still drop or disable kcanary. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* nixos/tests: Add a test for boot stage 1aszlig2016-05-06
| | | | | | | | | | | | | | | | | | | | | | | | | | We already have a small regression test for #15226 within the swraid installer test. Unfortunately, we only check there whether the md kthread got signalled but not whether other rampaging processes are still alive that *should* have been killed. So in order to do this we provide multiple canary processes which are checked after the system has booted up: * canary1: It's a simple forking daemon which just sleeps until it's going to be killed. Of course we expect this process to not be alive anymore after boot up. * canary2: Similar to canary1, but tries to mimick a kthread to make sure that it's going to be properly killed at the end of stage 1. * canary3: Like canary2, but this time using a @ in front of its command name to actually prevent it from being killed. * kcanary: This one is a real kthread and it runs until killed, which shouldn't be the case. Tested with and without 67223ee and everything works as expected, at least on my machine. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* nixos/tests/installer/swraid: Check for safemodeaszlig2016-05-06
| | | | | | | | This is a regression test for #15226, so that the test will fail once we accidentally kill one or more of the md kthreads (aka: if safe mode is enabled). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Merge pull request #14957 from dezgeg/gummiboot-testzimbatm2016-05-05
|\ | | | | NixOS installer tests: Add a test using Gummiboot
| * NixOS installer tests: Add a test using GummibootTuomas Tynkkynen2016-04-24
| | | | | | | | Issue #14956
* | nixos/tests/containers: Remove unused module argaszlig2016-05-04
| | | | | | | | | | | | | | | | | | Just removing the system argument because it doesn't exist (it's actually config.nixpkgs.system, which we're already using). We won't get an error anyway if we're not actually using it, so this is just an aesthetics fix. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* | nixos/tests/containers-imperative: Fix testaszlig2016-05-04
| | | | | | | | | | | | | | | | | | | | | | | | | | Make sure that we always have everything available within the store of the VM, so let's evaluate/build the test container fully on the host system and propagate all dependencies to the VM. This way, even if there are additional default dependencies that come with containers in the future we should be on the safe side as these dependencies should now be included for the test as well. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @kampfschlaefer, @edolstra
* | nixos/tests/chromium: Re-add map for all channelsaszlig2016-05-04
| | | | | | | | | | | | | | | | | | | | | | | | This partially reverts f2d24b98408b48c2179b131fa4c3700dc41f5b52. Instead of disabling the channels via removing the channel mapping from the tests themselves, let's just explicitly reference the stable test in release.nix. That way it's still possible to run the beta and dev tests via something like "nix-build nixos/tests/chromium.nix -A beta" and achieve the same effect of not building beta and dev versions on Hydra. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* | chromium: Disable Hydra builds of -dev and -betaEelco Dolstra2016-05-04
| | | | | | | | | | | | It's not the job of Nixpkgs to distribute beta versions of upstream packages. More importantly, building these delays channel updates by several hours, which is bad for our security fix turnaround time.
* | nixos/tests/netboot: Fix evaluation erroraszlig2016-05-03
| | | | | | | | | | | | | | | | | | Regression introduced by dfe608c8a2ecfdf0ab2838a967440207250a0b95. The commit turns the two arguments into one attrset argument so we need to adapt that to use the new calling convention. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* | installer: simple PXE bootable NixOS installerNahum Shalman2016-04-29
| | | | | | | | | | | | | | The Nix store squashfs is stored inside the initrd instead of separately (cherry picked from commit 976fd407796877b538c470d3a5253ad3e1f7bc68) Signed-off-by: Domen Kožar <domen@dev.si>
* | Merge pull request #14018 from ↵Franz Pletz2016-04-24
|\ \ | |/ |/| | | | | kampfschlaefer/feature/hostbridge_and_ipv6_for_containers containers: hostbridge and IPv6
| * containers tests: Distinguish declarative and imperative containersArnold Krille2016-04-02
| |
| * containers: Add more tests for ipv6 and hostbridgeArnold Krille2016-04-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | A testcase each for - declarative ipv6-only container Seems odd to define the container IPs with their prefix length attached. There should be a better way… - declarative bridged container Also fix the ping test by waiting for the container to start When the ping was executed, the container might not have finished starting. Or the host-side of the container wasn't finished with config. Waiting for 2 seconds in between fixes this.
* | cups tests: finally fix themVladimír Čunát2016-04-23
| | | | | | | | Fixes #14748.
* | Revert "nixos.tests.printing: fix"Joachim Fasting2016-04-18
| | | | | | | | | | | | This reverts commit 49894ac857fd1206ac111d6adbf6e9f6e640d795. Reverting in deference to https://github.com/NixOS/nixpkgs/issues/14782
* | nixos.tests.printing: fixJoachim Fasting2016-04-18
| | | | | | | | | | | | | | | | | | | | | | | | Two fixes: Not really sure why removing `--fail` from the curl calls is necessary, but with that option, curl erronously reports 404 (which it shouldn't per my interactive vm testing). Fix paths to example files used for the printing test Toghether, these changes allow the test to run to completion on my machine.
* | Merge pull request #14476 (taskserver)aszlig2016-04-15
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a Taskserver module along with documentation and a small helper tool which eases managing a custom CA along with Taskserver organisations, users and groups. Taskserver is the server component of Taskwarrior, a TODO list application for the command line. The work has been started by @matthiasbeyer back in mid 2015 and I have continued to work on it recently, so this merge contains commits from both of us. Thanks particularly to @nbp and @matthiasbeyer for reviewing and suggesting improvements. I've tested this with the new test (nixos/tests/taskserver.nix) this branch adds and it fails because of the changes introduced by the closure-size branch, so we need to do additional work on base of this.
| * | nixos/taskserver/helper: Improve CLI subcommandsaszlig2016-04-12
| | | | | | | | | | | | | | | | | | | | | Try to match the subcommands to act more like the subcommands from the taskd binary and also add a subcommand to list groups. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
| * | nixos/taskserver: Set allowedTCPPorts accordinglyaszlig2016-04-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As suggested by @matthiasbeyer: "We might add a short note that this port has to be opened in the firewall, or is this done by the service automatically?" This commit now adds the listenPort to networking.firewall.allowedTCPPorts as soon as the listenHost is not "localhost". In addition to that, this is now also documented in the listenHost option declaration and I have removed disabling of the firewall from the VM test. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
| * | nixos/taskserver: Don't change imperative usersaszlig2016-04-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Whenever the nixos-taskserver tool was invoked manually for creating an organisation/group/user we now add an empty file called .imperative to the data directory. During the preStart of the Taskserver service, we use process-json which in turn now checks whether those .imperative files exist and if so, it doesn't do anything with it. This should now ensure that whenever there is a manually created user, it doesn't get killed off by the declarative configuration in case it shouldn't exist within that configuration. In addition, we also add a small subtest to check whether this is happening or not and fail if the imperatively created user got deleted by process-json. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
| * | nixos/tests/taskserver: Make tests less noisyaszlig2016-04-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We were putting the whole output of "nixos-taskserver export-user" from the server to the respective client and on every such operation the whole output was shown again in the test log. Now we're *only* showing these details whenever a user import fails on the client. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
| * | nixos/taskserver/helper: Implement deletionaszlig2016-04-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Now we finally can delete organisations, groups and users along with certificate revocation. The new subtests now make sure that the client certificate is also revoked (both when removing the whole organisation and just a single user). If we use the imperative way to add and delete users, we have to restart the Taskserver in order for the CRL to be effective. However, by using the declarative configuration we now get this for free, because removing a user will also restart the service and thus its client certificate will end up in the CRL. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
| * | nixos/taskserver: Move .pki.fqdn to .fqdnaszlig2016-04-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's not necessarily related to the PKI options, because this is also used for setting the server address on the Taskwarrior client. So if someone doesn't have his/her own certificates from another CA, all options that need to be adjusted are in .pki. And if someone doesn't want to bother with getting certificates from another CA, (s)he just doesn't set anything in .pki. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
| * | nixos/taskserver: Rename .server options to .pkiaszlig2016-04-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After moving out the PKI-unrelated options, let's name this a bit more appropriate, so we can finally get rid of the taskserver.server thing. This also moves taskserver.caCert to taskserver.pki.caCert, because that clearly belongs to the PKI options. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
| * | nixos/taskserver: Rename server.{host,port}aszlig2016-04-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | Having an option called services.taskserver.server.host is quite confusing because we already have "server" in the service name, so let's first get rid of the listening options before we rename the rest of the options in that .server attribute. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
| * | nixos/tests/taskserver: Test imperative usersaszlig2016-04-11
| | | | | | | | | | | | | | | | | | | | | As the nixos-taskserver command can also be used to imperatively manage users, we need to test this as well. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
| * | nixos/taskserver: Rename nixos-taskdctlaszlig2016-04-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | Using nixos-taskserver is more verbose but less cryptic and I think it fits the purpose better because it can't be confused to be a wrapper around the taskdctl command from the upstream project as nixos-taskserver shares no commonalities with it. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
| * | nixos/tests: Add a test for the Taskserver serviceaszlig2016-04-05
| |/ | | | | | | | | | | | | | | | | | | | | | | A small test which checks whether tasks can be synced using the Taskserver. It doesn't test group functionality because I suspect that they're not yet implemented upstream. I haven't done an in-depth check on that but I couldn't find a method of linking groups to users yet so I guess this will get in with one of the text releases of Taskwarrior/Taskserver. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* | Merge branch 'staging', containing closure-size #7701Vladimír Čunát2016-04-13
|\ \
| * | installer tests: Use different package for testing `nix-env -iA`Tuomas Tynkkynen2016-04-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Coreutils is multi-output and the `info` output doesn't seem to be included on the install disk, failing like this (because now nix-env wants to build coreutils): ```` machine# these derivations will be built: machine# /nix/store/0jk4wzg11sa6cqyw8g7w5lb35axji969-bison-3.0.4.tar.gz.drv ... machine# /nix/store/ybjgqwxx63l8cj1s7b8axx09wz06kxbv-coreutils-8.25.drv machine# building path(s) ‘/nix/store/4xvdi5740vq8vlsi48lik3saz0v5jsx0-coreutils-8.25.tar.xz’ machine# downloading ‘http://ftpmirror.gnu.org/coreutils/coreutils-8.25.tar.xz’... machine# error: unable to download ‘http://ftpmirror.gnu.org/coreutils/coreutils-8.25.tar.xz’: Couldn't resolve host name (6) machine# builder for ‘/nix/store/5j3bc5sjr6271fnjh9gk9hrid8kgbpx3-coreutils-8.25.tar.xz.drv’ failed with exit code 1 machine# cannot build derivation ‘/nix/store/ybjgqwxx63l8cj1s7b8axx09wz06kxbv-coreutils-8.25.drv’: 1 dependencies couldn't be built machine# error: build of ‘/nix/store/ybjgqwxx63l8cj1s7b8axx09wz06kxbv-coreutils-8.25.drv’ failed ````
| * | Merge 'staging' into closure-sizeVladimír Čunát2016-04-07
| |\| | | | | | | | | | | | | | | | This is mainly to get the update of bootstrap tools. Otherwise there were mysterious segfaults: https://github.com/NixOS/nixpkgs/pull/7701#issuecomment-203389817
| * | Merge branch 'master' into closure-sizeVladimír Čunát2016-04-01
| |\ \ | | | | | | | | | | | | | | | | Beware that stdenv doesn't build. It seems something more will be needed than just resolution of merge conflicts.
| * \ \ Merge master into closure-sizeVladimír Čunát2016-03-08
| |\ \ \ | | | | | | | | | | | | | | | | | | | | The kde-5 stuff still didn't merge well. I hand-fixed what I saw, but there may be more problems.
| * \ \ \ Merge branch 'master' into closure-sizeVladimír Čunát2016-02-14
| |\ \ \ \
| * \ \ \ \ Merge recent 'staging' into closure-sizeVladimír Čunát2016-02-03
| |\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | Let's get rid of those merge conflicts.
| * \ \ \ \ \ Merge branch 'staging' into closure-sizeVladimír Čunát2016-01-19
| |\ \ \ \ \ \
| * \ \ \ \ \ \ Merge branch 'master' into closure-sizeVladimír Čunát2015-12-31
| |\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TODO: there was more significant refactoring of qtbase and plasma 5.5 on master, and I'm deferring pointing to correct outputs to later.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-07 21:40:51 +0000