tools: exit successfully if call trace is not from alsa

[aiChaoSONG]

Previouly, every call trace will fail the test
case, that's not correct. Only ALSA related
call trace should fail the test case.

This patch checks call trace message, and
only failed test case with ALSA related
call trace.

fix #184

[Bin-QA]

almost is good

[marc-hb]

Ignoring the code style issues for now, this change ignores every single non-snd Call Trace in every test, correct? That's extremely dangerous. Issue #167 is about ignoring one specific trace in one specific test.

More generally speaking, could the majority of this script be replaced by something much shorter like this?

journalctl --dmesg -p 3 | grep -v -e '$ignore_issue_123" -e "$ignore_dma_trace"

[aiChaoSONG]

@marc-hb Sorry for made a mistake. the issue should be #184 , not #167. #184 reported "a none SOF call trace caused one test case failed", but in fact that call trace is related to sound. As you said, ignore all call traces other than sound is dangerous. Let's close this for the issue is related to sound. I will try to use journalctl to refine error collection in another PR.

[aiChaoSONG]

@Bin-QA I think Marc's suggestion is good, is there any possibility to use this: journalctl --dmesg -p 3 | grep -v -e '$ignore_issue_123" -e "$ignore_dma_trace"

[Bin-QA]

how to clean buffer?
we force on current, like current case, current loop
so we need to clean the buffer
we not just force the kernel boot log

@aiChaoSONG it can use for upgrade: tools/sof-kernel-dump.sh
for the current kernel dump

[marc-hb]

test3_start=$(date +%s)
run_test3
test3_end=$(date +%s)
journalctl --boot --since=@"$test3_start" --until=@"$test3_end"

dmesg -c is more like a hack.

[marc-hb]

Longer example

test3_start=$(date +%s)
run_test3
test3_end=$(date +%s)
# Errors or worse
journalctl --boot --since=@"$test3_start" --until=@"$test3_end" -p 3
# Warnings only
journalctl --boot --since=@"$test3_start" --until=@"$test3_end" -p 4..4