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

Testcase that looks for BUG: or WARNING: in dmesg #442

Open
fbezdeka opened this issue May 5, 2023 · 3 comments
Open

Testcase that looks for BUG: or WARNING: in dmesg #442

fbezdeka opened this issue May 5, 2023 · 3 comments

Comments

@fbezdeka
Copy link

fbezdeka commented May 5, 2023

Hi all,

is there really no test case that checks if a kernel warning or bug occurred during the runtime of all or a specific test suite?

I already asked the question in [1] a few month ago but got no answer.
From time to time we can reproduce warnings or even bugs during the runtime of our own test suite.
It took some time to realize that we have real problems as LAVA jobs were marked as "green" or successful.

Yes, of course, I could implement such a check on my own (inline testsuite or even a complete test definition repo) but isn't that something that should be provided here as well?

Did I overlook something?

[1] https://git.lavasoftware.org/lava/lava/-/issues/576

@mwasilew
Copy link
Contributor

IMHO you're asking in the wrong place. test-definitions are not LAVA and I believe you're looking for LAVA feature.

@patersonc
Copy link
Contributor

Hi @fbezdeka

I wouldn't call it a "suite", but the KernelCI project runs a simple dmesg check script that will run in a generic LAVA environment with some minor changes. It could be a useful starting point for you.

Maybe we could get something similar added to this repo?

@ivoire
Copy link
Collaborator

ivoire commented Apr 18, 2024

Hello,

is there really no test case that checks if a kernel warning or bug occurred during the runtime of all or a specific test suite?

You can parse dmesg output after a set of tests.

I already asked the question in [1] a few month ago but got no answer. From time to time we can reproduce warnings or even bugs during the runtime of our own test suite. It took some time to realize that we have real problems as LAVA jobs were marked as "green" or successful.

The project moved to gitlab.com/lava/lava, so the answer is https://gitlab.com/lava/lava/-/issues/576 now.

Yes, of course, I could implement such a check on my own (inline testsuite or even a complete test definition repo) but isn't that something that should be provided here as well?

It should be possible to extend the current LAVA code to support such use-case.

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

No branches or pull requests

4 participants