Skip to content

Add initial run.sh for Kernel_Selftests with basic execution and result logging #62

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

smuppand
Copy link
Contributor

@smuppand smuppand commented Jun 3, 2025

This patch introduces the initial run.sh script for executing Kernel_Selftests within the qcom-linux-testkit framework. Key features include:

  • Basic support for executing kernel selftests from /kselftest based on a whitelist.

  • Logs individual test outcomes (PASS/FAIL/SKIP) to Kernel_Selftests.tests.

  • Summarizes overall result to Kernel_Selftests.res for CI integration.

  • Supports both run_test.sh scripts and standalone test binaries.

  • Architecture-based filtering via enabled_tests.list.

This provides the foundation for validating kernel selftests on Qualcomm platforms and integrates with existing test automation flows.

@vnarapar 

…nner

- Added (or improved) validation to ensure that the enabled_tests.list whitelist file is present and non-empty before executing kernel selftests.
- Script now also checks for the presence of the /kselftest directory and fails early with a clear error if missing.
- This prevents silent failures and improves CI robustness by guaranteeing that test configuration and dependencies are always validated before running.
- Logs explicit error messages for missing or empty enabled_tests.list and for missing /kselftest.
- Follows community best practices for test automation, as seen in major kernel CI flows.

Signed-off-by: Srikanth Muppandam <[email protected]>
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

Successfully merging this pull request may close these issues.

1 participant