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

kselftest:alsa-mixer regression on kevin #146

Closed
r-c-n opened this issue Dec 2, 2022 · 3 comments
Closed

kselftest:alsa-mixer regression on kevin #146

r-c-n opened this issue Dec 2, 2022 · 3 comments

Comments

@r-c-n
Copy link

r-c-n commented Dec 2, 2022

https://linux.kernelci.org/test/case/id/636251e552251d525ee7db67/

The test seems to be failing due to a timeout. Testing with a more permissive timeout shows that the test works fine (see https://lava.collabora.dev/scheduler/job/7930394#L1869 with a longer timeout vs https://lava.collabora.dev/scheduler/job/7929323#L1882 with the default one).

Unfortunately, the kselftest runner script hardcodes the timeout interval to 45 seconds and there don't seem to be any provisioning for overriding this in a per-test basis.

The proper solution for this would be to implement some kind of test-specific timeout definition and define a reasonable timeout for this test.

@r-c-n
Copy link
Author

r-c-n commented May 15, 2023

Following up Nicolas' patch and the conversation with Shuah: https://lore.kernel.org/linux-kselftest/[email protected]/T/#t

@r-c-n
Copy link
Author

r-c-n commented Jun 21, 2023

The kselftests timeouts can now be overridden by specifying a custom value using a command line option (--override-timeout): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f6a01213e3f8

So in theory this problem can be fixed by changing how KernelCI launches the tests, FYI @nuclearcat @gctucker

@padovan
Copy link
Contributor

padovan commented Jul 9, 2024

Old issue. (also we are not tracking kernel test failure/issues through GitHub anymore)

@padovan padovan closed this as completed Jul 9, 2024
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

2 participants