gen_sc7180_bl31_depthcharge_boot_yaml.sh: Use more reliable test patterns
"INFO: BL31: Initializing runtime services" message doesn't seem to be
output in the recent builds, beyond initial devel runs which were done
by Arthur on staging. (Alternatively, it's visible that many BL31's log
messages are not output/cut-off/char-lost across runs). So, check just
for the "depthcharge" and "This is a TF-A test build" messages.
Also, using "monitors" LAVA test method for individual (non-repeating)
messages is a hystorical workaround. Instead, "interactive" tests should
be used, which are more clear and scalable (albeit perhaps more verbose
to define).
Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
Change-Id: I55432d24d768d5f8bd121b47598ced515e90e2f9
1 file changed