Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 95ce5f29 authored by Paul E. McKenney's avatar Paul E. McKenney
Browse files

torture: Add a script to edit output from failed runs 



This commit adds a script that allows viewing the build and/or
console output from failed rcutorture, locktorture, or rcuperf runs.
This replaces a time-honored but inefficient manual procedure that uses
cut and paste.

Signed-off-by: default avatarPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Tested-by: default avatarNicholas Piggin <npiggin@gmail.com>
parent 60cc43fc

tools/testing/selftests/rcutorture/bin/kvm-find-errors.sh

0 → 100755
+55 −0
Original line number Diff line number Diff line 
#!/bin/sh

#

# Invoke a text editor on all console.log files for all runs with diagnostics,

# that is, on all such files having a console.log.diags counterpart.

# Note that both console.log.diags and console.log are passed to the

# editor (currently defaulting to "vi"), allowing the user to get an

# idea of what to search for in the console.log file.

#

# Usage: kvm-find-errors.sh directory

#

# The "directory" above should end with the date/time directory, for example,

# "tools/testing/selftests/rcutorture/res/2018.02.25-14:27:27".



rundir="${1}"

if test -z "$rundir" -o ! -d "$rundir"

then

	echo Usage: $0 directory

fi

editor=${EDITOR-vi}



# Find builds with errors

files=

for i in ${rundir}/*/Make.out

do

	if grep -q "error:" < $i

	then

		files="$files $i"

	fi

done

if test -n "$files"

then

	$editor $files

else

	echo No build errors.

fi

if grep -q -e "--buildonly" < ${rundir}/log

then

	echo Build-only run, no console logs to check.

fi



# Find console logs with errors

files=

for i in ${rundir}/*/console.log

do

	if test -r $i.diags

	then

		files="$files $i.diags $i"

	fi

done

if test -n "$files"

then

	$editor $files

else

	echo No errors in console logs.

fi