Skip to content

Failure to start logger does not fail immediately, only at the end of the test #506

@ranj063

Description

@ranj063

If the logger fails to start for some reason, the test result is reported as a FAIL. In this case, the test should report the correct status and warn that logger output is unavailable. For example, I have an error with starting logger as follows:
"error: src hash value from version file (0x35cdfa4f) differ from src hash version saved in dictionary (0xfb141ec0)."

But the test, check-playback.sh, runs through all the loops and PCM devices and results in a FAIL at the end when the test itself was actually a PASS.

2020-11-09 21:21:23 UTC [INFO] ===== Testing: (Round: 1/1) (PCM: Speakers [hw:0,5]) (Loop: 3/3) =====
2020-11-09 21:21:23 UTC [COMMAND] aplay -Dhw:0,5 -r 48000 -c 2 -f S16_LE -d 10 /dev/zero -v -q
Hardware PCM card 0 'sof-cml_rt1011_rt5682' device 5 subdevice 0
Its setup is:
stream : PLAYBACK
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 2
rate : 48000
exact rate : 48000 (48000/1)
msbits : 16
buffer_size : 16384
period_size : 4096
period_time : 85333
tstamp_mode : NONE
tstamp_type : MONOTONIC
period_step : 1
avail_min : 4096
period_event : 0
start_threshold : 16384
stop_threshold : 16384
silence_threshold: 0
silence_size : 0
boundary : 4611686018427387904
appl_ptr : 0
hw_ptr : 0
2020-11-09 21:21:33 UTC [INFO] pkill -TERM sof-logger
2020-11-09 21:21:33 UTC [ERROR] sof-logger was already dead
2020-11-09 21:21:34 UTC [INFO] nlines=1 /root/sof-test/logs/check-playback/2020-11-09-13:19:01-2579/slogger.txt
2020-11-09 21:21:34 UTC [INFO] Test Result: FAIL!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions