torture: Place console.log files correctly from the get-go
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Tue, 1 Dec 2015 23:53:11 +0000 (15:53 -0800)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Sun, 6 Dec 2015 01:58:34 +0000 (17:58 -0800)
commitc979ff991764a2e620db0b1bfb0a105b9cf78b6a
tree0831a0424c300d8fabe125bbbc60035cba5797c3
parent5708c6475789ac5f58ff620e78bd08ca2caa1f23
torture: Place console.log files correctly from the get-go

Currently, the console output files ("console.log") are placed in the
build directory initially, then copied to the results directory.
One problem with this is if a qemu refuses to die in a timely fashion
after a kernel hang, it will continue to write after the next qemu
starts up, resulting in confusing output from the old instance of
qemu.  This commit prevents such confusion by placing the console.log
files into the results directory to begin with, so that a given instance
of qemu is always writing only to its own console.log file.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
tools/testing/selftests/rcutorture/bin/kvm-test-1-run.sh