Skip to content

Basline testing: Analyze failures because of some error message from kernel #463

@musamaanjum

Description

@musamaanjum

The baseline or boot tests boot the kernel and check if there is any log present in crit, alert and emerg levels. If the error is present, the boot test is marked as failed, otherwise the test passes:

crit --result pass --measurement 0 --units lines
alert --result pass --measurement 0 --units lines
emerg --result pass --measurement 0 --units lines

If any error/warning log is present on these levels, the crit, alert and emerge subtests are failed. Hence, the boot test fails. The log examples:

kern  :emerg : call_irq_handler: 2.55 No irq handler for vector
kern  :emerg : call_irq_handler: 1.55 No irq handler for vector
kern  :emerg : call_irq_handler: 3.55 No irq handler for vector

These logs mean that there wasn't any handler available when the interrupt arrived.

There are more kinds of errors which should be investigated and resolved to get more cleaner results.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions