• Paul E. McKenney's avatar
    torture: Make kvm-remote.sh announce which system is being waited on · ab69d3c8
    Paul E. McKenney authored
    If a remote system fails in certain ways, for example, if it is rebooted
    without removing the contents of the /tmp directory, its remote.run file
    never will be removed and the kvm-remote.sh script will loop waiting
    forever.  The manual workaround for this (hopefully!) rare event is to
    manually remove the file, which will cause the results up to the reboot
    to be collected and evaluated.
    
    Unfortunately, to work out which system is holding things up, the user
    must refer to the name of the last system whose results were collected,
    then look up the name of the next system in sequence, then manually
    remove the remote.run file.  Even more unfortunately, this procedure can
    be fooled in runs where each system handles more than one batch should
    a given system take longer than expected, causing the systems to be
    handled out of order.
    
    This commit therefore causes kvm-remote.sh to print out the name of
    the system it will wait on next, allowing the user to refer directly
    to that name.  Making the kvm-remote.sh script automatically handle
    unscheduled termination of the qemu processes is left as future work.
    Quite possibly deep future work.
    Signed-off-by: default avatarPaul E. McKenney <paulmck@kernel.org>
    ab69d3c8
kvm-remote.sh 7.69 KB