Repository navigation
Conversation
LAVA fails the job if a dependency_path entry matches nothing or points outside the repository. Check it in validate.py too, so CI finds it first. Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
The tests need sh-test-lib and send-to-lava.sh. ltp and kselftest also need skipgen. With dependency_path LAVA copies 2M to 5M to the DUT instead of the whole repository. Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
Add a short example, and say when skipgen and .git must be listed. Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
Add "Lava-Test Test Definition 2.0". It no longer requires the 'os' and 'devices' metadata keys: where a test runs is decided by the test plan or the LAVA job, not by the test definition. 'os', 'scope' and 'devices' are optional and still accepted when present. 2.0 requires 'dependency_path', so LAVA copies only the files the test needs to the DUT instead of the whole repository. The entries are checked by the existing dependency_path validation. 2.0 files must contain 'name', 'format', 'description', 'maintainer' and 'dependency_path'. 1.0 test definitions are still accepted with unchanged rules. validate.py now keeps the mandatory keys for each format in a single table and checks the format first, so it decides which rules apply. Unknown formats report the list of supported values. generate_test_docs.py omits empty OS/Scope/Devices sections, and testplan2html.py no longer fails when 'os' or 'scope' are missing. Assisted-By: Claude Opus 5.5 Signed-off-by: Milosz Wasilewski <milosz.wasilewski@oss.qualcomm.com>
Add "Manual Test Definition 2.0". Like "Lava-Test Test Definition 2.0", 'name', 'format', 'description' and 'maintainer' are mandatory, while 'os', 'scope' and 'devices' are optional. 'dependency_path' stays optional for manual tests: they are not run by LAVA copying the repository to the DUT, so the key has no effect there. "Manual Test Definition 1.0" files are still accepted with unchanged rules. test-runner.py detects manual tests by the "Manual Test Definition" prefix, so it handles 2.0 files without changes. Assisted-By: Claude Opus 5.5 Signed-off-by: Milosz Wasilewski <milosz.wasilewski@oss.qualcomm.com>
Collaborator
|
Looks interesting @mwasilew thank you. As we discussed offline, lets bring this up in the lava meeting on Monday. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add Test Definition 2.0 format YAML files. The new format changes the list of mandatory metadata fields and updates the test definition validation.