_get_current_dmesg can be used to grep customized pattern.
Signed-off-by: Liu Bo <bo.li.liu@xxxxxxxxxx>
---
common/rc | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/common/rc b/common/rc
index 78a2101..111ed69 100644
--- a/common/rc
+++ b/common/rc
@@ -3215,6 +3215,12 @@ _get_device_size()
grep `_short_dev $1` /proc/partitions | awk '{print $3}'
}
+# get current dmesg log
+_get_current_dmesg()
+{
+ dmesg | tac | sed -ne "0,\#run fstests $seqnum at $date_time#p" | tac
+}
+
# check dmesg log for WARNING/Oops/etc.
_check_dmesg()
{
@@ -3230,8 +3236,7 @@ _check_dmesg()
# search the dmesg log of last run of $seqnum for possible failures
# use sed \cregexpc address type, since $seqnum contains "/"
- dmesg | tac | sed -ne "0,\#run fstests $seqnum at $date_time#p" | \
- tac | $filter >$seqres.dmesg
+ _get_current_dmesg | $filter >$seqres.dmesg
grep -q -e "kernel BUG at" \
-e "WARNING:" \
-e "BUG:" \
--
2.5.0
--
To unsubscribe from this list: send the line "unsubscribe fstests" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
