action #28027
closed
Add function to account for the unexpected in serial output
Added by coolo over 6 years ago.
Updated about 6 years ago.
Description
We want a test to fail properly if the kernel output OOPS or BUG, but we can't always hook this into specific tests.
So we need a hook in the distribution to check the serial0.txt for regexps given in main.pm - and either generate soft failure or hard failure from the test.
See https://progress.opensuse.org/issues/18286 for a specific use case.
- Has duplicate action #18416: [tools][openqa][backend] Catch kernel opps on serial console / journal added
- Assignee set to dasantiago
- Status changed from New to In Progress
- Target version changed from Ready to Current Sprint
- % Done changed from 0 to 90
- Status changed from In Progress to Resolved
- Target version changed from Current Sprint to Done
Hi, can you say what fixed it and how we can make use of it in tests?
Aloha!:
You can take a look at this pr which is basically allowing you to use two type of regexps, that either will trigger a soft fail or a hard failure of a test based on what's being seen on serial output log file of the SUT if it's present.
szarate wrote:
Aloha!:
You can take a look at this pr which is basically allowing you to use two type of regexps, that either will trigger a soft fail or a hard failure of a test based on what's being seen on serial output log file of the SUT if it's present.
Yes :-)
On the main.pm you can define overall regular expressions for all the current set of tests. Example:
$testapi::distri->set_expected_serial_failures(soft=>[quotemeta 'THIS A PATTERN'], hard=>[qr/pattern.*?matched/])
You can also specify and override patterns specified in the tests:
sub run {
my ($self) = @_;
$self->set_expected_serial_failures(soft=>[quotemeta 'THIS A PATTERN'], hard=>[qr/pattern.*?matched/])
Let me know if you have any question.
Also available in: Atom
PDF