f65d548ac2
Without any swap space enabled, it's possible some intensive operation can chew up all the memory on the test VM. Enabling swap space will prevent this for minor cases, but could lead to disk-thrashing if the memory demand is excessive. Since the test system never reboots, using a file-backed swap should suffice. Though not ideal, it's easy to setup and doesn't require any interactions with the cloud that owns the VM or the job that created it. Signed-off-by: Chris Evich <cevich@redhat.com> |
||
|---|---|---|
| .. | ||
| cni | ||
| rpm | ||
| systemd | ||
| test | ||