1. 16 5月, 2018 1 次提交
    • P
      torture: Fold parse-torture.sh into parse-console.sh · d600e06b
      Paul E. McKenney 提交于
      The rcutorture scripting scans the console output twice, once to look
      for various sorts of hangs and again to find warnings and panics.
      Unfortunately, only the output of the second scan gets written to the
      console.log.diags file, which can cause hangs to be overlooked.
      This commit therefore folds the parse-torture.sh script (which looks
      for hangs) into the parse-console.sh script (which looks for warnings
      and panics).  This allows both types of failure information to be
      added to console.log.diags, while still reliably removing this file
      when it proves to be empty.
      
      This also fixes a long-standing bug where rcuperf log files would
      unconditionally complain about a hang.
      Signed-off-by: NPaul E. McKenney <paulmck@linux.vnet.ibm.com>
      Tested-by: NNicholas Piggin <npiggin@gmail.com>
      d600e06b
  2. 15 6月, 2016 1 次提交
  3. 26 1月, 2016 3 次提交
  4. 06 12月, 2015 1 次提交
    • P
      torture: Abbreviate console error dump · 5708c647
      Paul E. McKenney 提交于
      Currently, the scripts print a list of warning/bug indicators from the
      console.log file.  This works well if there are only a few warnings or
      bugs, but can be quite annoying if there is a large number.  This commit
      therefore prints a summary listing the number of each type of warning/bug
      indicator, but only if there is at least one such indicator.  The full
      list is stored in the results directory at console.log.diags, which
      makes it easier to find the warning/bugs in the full console.log.
      Signed-off-by: NPaul E. McKenney <paulmck@linux.vnet.ibm.com>
      Reviewed-by: NJosh Triplett <josh@joshtriplett.org>
      5708c647
  5. 07 1月, 2015 1 次提交
  6. 08 9月, 2014 3 次提交
  7. 04 12月, 2013 3 次提交