[PATCH] Use unsafe caching during kickstart tests.
Vratislav Podzimek
vpodzime at redhat.com
Fri Oct 30 12:43:39 UTC 2015
On Thu, 2015-10-29 at 11:50 -0400, Chris Lumens wrote:
> This doesn't seem to do anything bad, and it does speed up each test by
> several minutes in my very unscientific checking.
> ---
> tests/kickstart_tests/scripts/run_one_ks.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/kickstart_tests/scripts/run_one_ks.sh
> b/tests/kickstart_tests/scripts/run_one_ks.sh
> index 9e86dfa..7def0ab 100755
> --- a/tests/kickstart_tests/scripts/run_one_ks.sh
> +++ b/tests/kickstart_tests/scripts/run_one_ks.sh
> @@ -95,7 +95,7 @@ runone() {
> fi
>
> disks=$(prepare_disks ${tmpdir})
> - disk_args=$(for d in $disks; do echo --disk $d; done)
> + disk_args=$(for d in $disks; do echo --disk $d,cache=unsafe; done)
>
> echo "PYTHONPATH=$PYTHONPATH"
> eval ${KSTESTDIR}/scripts/kstest-runner ${kargs} \
ACK. This is what I use for all my testing VMs and I can confirm it makes a huge
difference. Never had any troubles with it.
--
Vratislav Podzimek
Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic
More information about the anaconda-patches
mailing list