| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
And adopt the tests to add an interface and remove it again.
It should work when deactivating rstp, it will not work when activating
rstp for the first bridge as then the userspace daemon is not yet
available. But once one bridge is active with stp, it should work with
the reload for any further bridge.
Fixes #21745. Also see #22547.
|
| | |
|
| |
|
|
| |
cc #23279
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit b806e25d65421d7aa0a524ce1601f0e51099df11.
This seems to push Hydra's memory usage out of the roof fail nixos
evaluating with:
Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
Let's revert this for now. It's not a big deal at all since the
nixpkgs-unstable jobset is still building the packages.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Excluding modules/programs/environment.nix for PATHand QT_PLUGIN_PATH to allow the programs to continue running.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
The test starts the glance service, creates a nixos image and ensures Glance
list it.
Note the test also starts the Keystone service since it is required
by Glance.
|
| | |
|
| | |
|
| |
|
|
| |
cc #20557
|
| |
|
|
| |
This reverts commit 0ba3d429a758cec15545fc11c9d3fd1424c5c5f8.
|
| |
|
|
|
|
|
|
|
| |
Since 8180922d236c53b5e09cfe1b63f6c12977bb2803, the cjdns module
imports from a derivation, which is very bad. It causes all of stdenv
to be built at evaluation time. Since we have a hard 3600 second limit
on Hydra evaluations, this was causing NixOS jobsets to time out.
@joachifm
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Test that adding physical devices to containers works, find that network setup
then doesn't work because there is no udev in the container to tell systemd
that the device is present.
Fixed by not depending on the device in the container.
Activate the new container test for release
Bonds, bridges and other network devices need the underlying not as
dependency when used inside the container. Because the device is already
there.
But the address configuration needs the aggregated device itself.
|
| | |
|
| | |
|
| |
|
|
| |
https://github.com/NixOS/nixpkgs/issues/18209#issuecomment-246763699
|
| |
|
|
|
| |
(cherry picked from commit d171c59926b77564089964f06ba761609b9a477e)
Signed-off-by: Domen Kožar <domen@dev.si>
|
| |
|
|
| |
(cherry picked from commit 701f02a6eed902835e3d2a27838723cd9a7bb66a)
|
| |\
| |
| | |
ferm: add integration test
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
| |
This reverts commit 9e6eec201b8b56ef493c60af3acb2e8ddd8be258.
Verified locally that cd063d7 fixes the problem.
cc @edolstra @aszlig
|
| |
|
|
|
|
|
|
| |
It's hanging and blocking the unstable channel.
http://hydra.nixos.org/build/38984676
@aszlig
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It uses import-from-derivation, which is a bad thing, because this
causes hydra-evaluator to build Cassandra at evaluation time.
$ nix-instantiate nixos/release.nix -A tests.cassandra.i686-linux --dry-run
error: cannot read ‘/nix/store/c41blyjz6pfvk9fnvrn6miihq5w3j0l4-cassandra-2.0.16/conf/cassandra-env.sh’, since path ‘/nix/store/0j9ax4z8xhaz5lhrwl3bwj10waxs3hgy-cassandra-2.0.16.drv’ is not valid, at /home/eelco/Dev/nixpkgs/nixos/modules/services/databases/cassandra.nix:373:11
Also, the module is a mess (bad option descriptions, poor indentation,
a gazillion options where a generic "config" option would suffice, it
opens ports in the firewall, it sets vm.swappiness, ...).
|
| |\
| |
| | |
Cassandra
|
| | |
| |
| |
| |
| |
| | |
The module will configure a Cassandra server with common options being
tweakable. Included is also a test which will spin up 3 nodes and
verify that the cluster can be formed, broken, and repaired.
|
| | | |
|
| | |
| |
| |
| |
| | |
PDF is very 20th century and nobody reads technical documentation this
way anymore.
|
| |/
|
|
|
|
|
|
| |
With these changes, a container can have more then one veth-pair. This allows for example to have LAN and DMZ as bridges on the host and add dedicated containers for proxies, ipv4-firewall and ipv6-firewall. Or to have a bridge for normal WAN, one bridge for administration and one bridge for customer-internal communication. So that web-server containers can be reached from outside per http, from the management via ssh and can talk to their database via the customer network.
The scripts to set up the containers are now rendered several times instead of just one template. The scripts now contain per-container code to configure the extra veth interfaces. The default template without support for extra-veths is still rendered for the imperative containers.
Also a test is there to see if extra veths can be placed into host-bridges or can be reached via routing.
|
| | |
|
| |
|
|
|
|
|
| |
GoCD is an open source continuous delivery server specializing in advanced workflow
modeling and visualization. Update maintainers list to include swarren83. Update
module list to include gocd agent and server module. Update packages list to include
gocd agent and server package. Update version, revision and checksum for GoCD
release 16.5.0.
|
| |
|
|
| |
Includes a module for service setup and a test
to verify functionality of both service and pkg.
|
| | |
|
| |
|
| |
Would have caught regression #16766
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
For consistency, and in case we ever want to support another
architecture.
|