| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | nixos/tests/networking: Expose subtests via attrs | aszlig | 2016-03-01 |
| | | | | | | | | | | | | | | | | So far the networking test expression only generated a single test depending on the passed "test" attribute. This makes it difficult to autodiscover the subtests with our shiny new callSubTests function. This change essentially doesn't change the behaviour of the subtests but rather exposes them as an attribute set instead of relying on a particular input argument. The useNetworkd argument still exists however. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @wkennington | ||
| * | nixos/tests/networking: Add a test for loopback | aszlig | 2015-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> | ||
| * | all tests: added meta.maintainers section | Joachim Schiele | 2015-07-12 |
| | | |||
| * | nixos/tests/networking: Clean up and attempt to make more reliable | William A. Kennington III | 2015-04-10 |
| | | |||
| * | nixos/network: Remove debug output in tests | William A. Kennington III | 2014-11-30 |
| | | |||
| * | nixos/networking: More fixes | William A. Kennington III | 2014-11-29 |
| | | |||
| * | nixos/tests: Add networking tests for basic functionality | William A. Kennington III | 2014-11-29 |