cicd: Consider oom-killer a crash when processing logs.

This commit is contained in:
Ben Greear
2020-06-04 06:12:33 -07:00
parent 9bf6cacc29
commit a327818014
2 changed files with 3 additions and 1 deletions

View File

@@ -79,7 +79,7 @@ DPT_CFG=ben
SCENARIO=tip-auto
RPT_TMPDIR=${MY_TMPDIR}/lf_reports
LF_SER_DEV=$(basename $LF_SERIAL)
DUT_SER_DEV=$(basename $DUT_SERIAL)
DUT_SER_DEV=$(basename $AP_SERIAL)
LF_SER_LOG=$MY_TMPDIR/lanforge_console_log_$LF_SER_DEV.txt
DUT_SER_LOG=$MY_TMPDIR/dut_console_log_$DUT_SER_DEV.txt
REGLOG=$MY_TMPDIR/basic_regression_log_$$.txt

View File

@@ -231,6 +231,7 @@ sub processLogs {
($ln =~ /BUG:/) ||
($ln =~ /Hardware became unavailable during restart/) ||
($ln =~ /restarting hardware/) ||
($ln =~ /oom-killer/) ||
($ln =~ /crashed/)) {
if ($ln =~ /WARNING:/) {
$warnings++;
@@ -242,6 +243,7 @@ sub processLogs {
$restarting++;
}
elsif (($ln =~ /crashed/) || # software/firmware crashed
($ln =~ /oom-killer/) || # System OOM, processes were force-killed by kernel
($ln =~ /became unavailable/)) { # hardware crashed
$crashed++;
}