Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
musamaanjum opened this issue Oct 10, 2024 · 1 comment
Assignees

Comments

@musamaanjum
Copy link

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.

@musamaanjum musamaanjum self-assigned this Oct 10, 2024
@musamaanjum musamaanjum converted this from a draft issue Oct 10, 2024
@musamaanjum
Copy link
Author

Closing in favor of other tickets. This is a duplicate ticket.
#496
kernelci/kernelci-core#2483

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant