summary refs log tree commit diff
path: root/nixos/release.nix
Commit message (Collapse)AuthorAge
...
* 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.
* | 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>
* nixos/tests: Add a test for keyboard layoutsaszlig2016-03-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I had the basic version of this laying around for some while but didn't continue on it. Originally it was for testing support for the Neo layout introduced back then (8cd6d53). We only test the first three Neo layers, because the last three layers are largely comprised of special characters and in addition to that the support for the VT keymap seems to be limited compared to the Xorg keymap. Yesterday @NicolasPetton on IRC had troubles with the Colemak layout (IRC logs: http://nixos.org/irc/logs/log.20160330, starting at 16:08) and I found that test again, so I went for improving and adding to <nixpkgs>. While the original problem seemed to be related to GDM, we can still add another subtest that checks whether GDM correctly applies the keyboard layout. However I don't have a clue how to properly configure the keyboard layout on GDM, at least not within the NixOS configuration. The main goal of this test is not to test a complete set of all key mappings but to check whether the keymap is loaded and working at all. It also serves as an example for NixOS keyboard configurations. The list of keyboard layouts is by no means complete, so everybody is free to add their own to the test or improve the existing ones. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Build most ISOs/OVAs for x86_64-linux onlyEelco Dolstra2016-03-15
| | | | | | Probably not many people care about i686-linux any more, but building all these images is fairly expensive (e.g. in the worst case, every Nixpkgs commit would trigger a few gigabytes of uploads to S3).
* Combine ISO generation stepsEelco Dolstra2016-03-15
| | | | | This folds adding hydra-build-products into the actual ISO generation, preventing an unnecessary download of the ISO.
* Combine OVA generation stepsEelco Dolstra2016-03-15
| | | | | | | | Previously this was done in three derivations (one to build the raw disk image, one to convert to OVA, one to add a hydra-build-products file). Now it's done in one step to reduce the amount of copying to/from S3. In particular, not uploading the raw disk image prevents us from hitting hydra-queue-runner's size limit of 2 GiB.
* nixos/tests: implement dnscrypt-proxy testJoachim Fasting2016-03-11
| | | | | This test verifies that the daemon actually activates upon a user-initiated ping, when using the recommended configuration.
* nixos/release: Replace a: b: a // b by mergeAttrsaszlig2016-03-02
| | | | | | No change in functionality, it just looks nicer that way. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Merge pull request #13585 (nixos-tests-splitup)aszlig2016-03-01
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | This splits a few NixOS tests (namely Chromium, VirtualBox and the networking tests) into several subtests that are exposed via attributes. The networking tests were already split up but they didn't expose an attribute set of available tests but used a function attribute to specify the resulting test instead. A new function callSubTests in nixos/release.nix is now responsible for gathering subtests, which is also used for the installer and boot tests. The latter is now placed in a tests.boot.* namespace rather than "polluting" the tests attribute set with its subtest.
| * nixos/tests/chromium: Split up into subtestsaszlig2016-03-01
| | | | | | | | | | | | | | | | | | | | This makes it easier to test just a specific channel rather than to force testing all builds down the users/testers throat. Especially this makes it easier to test NixOS channel upgrades only against the Chromium stable channel instead of just removing the beta/dev channels from the tests entirely (as done in 69ec09f38aa1f1d37baec73ebdf9cf5f21050f94). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
| * nixos/release: Use callSubTests for subtestsaszlig2016-03-01
| | | | | | | | | | | | | | | | | | | | | | | | Should clean up a lot of these redundant lines for various sub-tests. Note that the tests.boot* are now called tests.boot.boot*, but otherwise all the test attribute names should stay the same. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @edolstra Cc: @wkennington Cc: @bobvanderlinden
| * nixos/release.nix: Add a callSubTests functionaszlig2016-03-01
| | | | | | | | | | | | | | | | | | | | | | | | | | This should de-clutter the various redundant lines of callTest's on subtests so that every main test file should have only one line with a callSubTests instead. Overrides work the same way as callTest, except that if the system attribute is explicitly specified we do not generate attributes for all available systems. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @edolstra
| * nixos/tests/virtualbox: Split up subtestsaszlig2016-02-29
| | | | | | | | | | | | | | | | | | | | | | | | Now subtests are separate derivations, because the individual tests do not depend on state from previous test runs. This has the advantage that it's easier to run individiual tests and it's also easier to pinpoint individual tests that randomly fail. I ran all of these tests locally and they still succeed. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* | Revert "Add the tool "nixos-typecheck" that can check an option declaration to:"Eelco Dolstra2016-03-01
| | | | | | | | | | | | This reverts commit cad8957eabcbf73062226d28366fd446c15c8737. It breaks NixOps, but more importantly, such major changes to the module system really need to be reviewed.
* | Merge pull request #10288 from lethalman/gnomeisoLuca Bruno2016-02-29
|\ \ | | | | | | installer: add graphical GNOME iso
| * | installer: add graphical GNOME isoLuca Bruno2016-02-29
| | |
* | | Add the tool "nixos-typecheck" that can check an option declaration to:Thomas Strobel2016-02-29
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | - Enforce that an option declaration has a "defaultText" if and only if the type of the option derives from "package", "packageSet" or "nixpkgsConfig" and if a "default" attribute is defined. - Enforce that the value of the "example" attribute is wrapped with "literalExample" if the type of the option derives from "package", "packageSet" or "nixpkgsConfig". - Warn if a "defaultText" is defined in an option declaration if the type of the option does not derive from "package", "packageSet" or "nixpkgsConfig". - Warn if no "type" is defined in an option declaration.
* | Revert "Add a way to pin a NixOS version within the module system."Eelco Dolstra2016-02-27
|/ | | | | | This reverts commit a5992ad61b314104aff7e28a41ce101a1b0e7c35. Motivation: https://github.com/NixOS/nixpkgs/commit/a5992ad61b314104aff7e28a41ce101a1b0e7c35#commitcomment-14986820
* Revert "Merge #12357: nixos docs: show references to packages"Vladimír Čunát2016-02-03
| | | | | | The PR wasn't good enough yet. This reverts commit b2a37ceeea8c38ec71447f8dae1e6890a8cf982d, reversing changes made to 7fa9a1abce623aaf18b22f5dca3fc8a44a494e8d.
* Merge #12357: nixos docs: show references to packagesVladimír Čunát2016-02-03
|\
| * nixos manuals: allow displaying package referencesVladimír Čunát2016-01-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The manuals are now evaluated with each derivation in `pkgs` (recursively) replaced by a fake with path "\${pkgs.path.to.the.attribute}". It isn't perfect, but it seems to cover a vast majority of use cases. Caveat: even if the package is reached by a different means, the path above will be shown and not e.g. `${config.services.foo.package}`. As before, defaults created by `mkDefault` aren't displayed, but documentation shouldn't (mostly) be a reason to use that anymore. Note: t wouldn't be enough to just use `lib.mapAttrsRecursive`, because derivations are also (special) attribute sets.
* | boot.initrd.network: Support DHCPEelco Dolstra2016-02-02
| | | | | | | | This allows us to use it for EC2 instances.
* | grsecurity: add NixOS VM testDan Peebles2016-01-24
| |
* | nixos: add test for postgresql, fixes #11146Rok Garbas2016-01-20
|/
* nixos/mathics: New service and testBenjamin Staffin2016-01-02
|
* amazon-image: enable configure-from-userdata and the corresponding VM testDan Peebles2015-12-30
|
* Add some preferLocalBuildEelco Dolstra2015-12-29
|
* nixos/tests/networking: Add a test for loopbackaszlig2015-12-18
| | | | | | | | | | | | | | | | It serves as a regression test, because right now if you enable networking.useNetworkd the default loopback interface doesn't get assigned any IP addresses. To be sure, I have bisected this and it has been introduced with the update to systemd 228 in 1da87d4. Only the "scripted" networking tests have to succeed in order to trigger a channel update of nixos-unstable, so I'm leaving this test as broken and we have to figure out next what's the *exact* reason for the breakage. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* nixos/tests: test SDDM with KDE 5 enabledThomas Tuegel2015-12-11
|
* nixos tests: pump.io: initRodney Lorrimar2015-12-06
|
* add nixos/tests/sddmThomas Tuegel2015-11-23
|
* Add a way to pin a NixOS version within the module system.Nicolas B. Pierron2015-11-19
| | | | | This modification add a way to re-evaluate the module system with a different version of NixOS, or with a different set of arguments.
* Disable the ec2-config testEelco Dolstra2015-09-28
| | | | | | "amazon-init.nix" is not included in the default AMIs because it unconditionally runs a nixos-rebuild. Also, the test has never worked (http://hydra.nixos.org/job/nixos/trunk-combined/nixos.tests.ec2-config).
* nixos tests: add gdm testLuca Bruno2015-09-15
|
* Disable lightdm testEelco Dolstra2015-08-17
| | | | | | | | It's hanging in the OCR step for hours. @aszlig http://hydra.nixos.org/build/24268601
* Disable system_tarball_pc and fix evalEelco Dolstra2015-07-22
| | | | | | It refers to a kernel version that no longer exists. (cherry picked from commit e4b9624ca89617005cb082e2a8301695759e1b19)
* all tests: added meta.maintainers sectionJoachim Schiele2015-07-12
|
* nixos/tests/installer: Add a testcase for fat32 /bootWilliam A. Kennington III2015-07-08
|
* Factor the NixOS channel building code out into its own file, so I can use ↵Dan Peebles2015-06-13
| | | | it elsewhere
* Initial attempt at configuring from EC2 userdata (with input from cstrahan). ↵Dan Peebles2015-06-11
| | | | Now with VM tests!
* Simple EC2 user-data VM testDan Peebles2015-06-11
|
* Installer tests: Don't use the ISOEelco Dolstra2015-06-10
| | | | | | | | | We already have separate tests for checking whether the ISO boots correctly, so it's not necessary to do that here. So now tests/installer.nix just tests nixos-install, from a regular NixOS VM that uses the host's Nix store. This makes running the tests more convenient because we don't have to build a new ISO after every change.
* nixos: Add lightdm test to release.nix.aszlig2015-05-28
| | | | | | | This is just to let it run on Hydra but doesn't have an affect on channel updates. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* nixos/release: Add luksroot test to "tested" job.aszlig2015-05-21
| | | | | | | | We want to avoid getting broken LUKS systems into the latest channel, so let's ensure that the channel update won't happen if LUKS support is broken again. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* nixos/release: Test vbox on x86_64-linux only.aszlig2015-04-04
| | | | | | | | | | | The i686-linux test has never worked and I wrote the VM test only on x86_64-linux to verify whether hardening mode works. I don't know why it fails on i686-linux, but that might be because the inner VirtualBox VM we're starting during the VM test doesn't use hardware virtualization. Closes #5708. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Add nfs4 testEelco Dolstra2015-04-02
|
* nixos: Re-add swraid installer tests to releases.aszlig2015-04-01
| | | | | | | | | | | | | | | | | | It has been removed by 71a197bc6e60c2c35687fc862cec9a0036a3877e. I'm reintroducing the test mainly because it actually *is* useful, because right now, machines with mdraid will not boot. In order to prevent such things from happening in the future, we should *not* remove this VM test again. If it really goes back to failing randomly, we should really try to fix it instead of removing it again. Of course it fails right now because of the mdraid bump in 7719f7f. Also, if you want to have additional info about the reasons, have a look at the commit message of 666cf992f05d20c537da7f495afe3622023495d2. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-04 06:39:59 +0000