Fix AudioRecord testcase ID collision for LAVA CI#383
Merged
smuppand merged 1 commit intoqualcomm-linux:mainfrom Apr 2, 2026
Merged
Fix AudioRecord testcase ID collision for LAVA CI#383smuppand merged 1 commit intoqualcomm-linux:mainfrom
smuppand merged 1 commit intoqualcomm-linux:mainfrom
Conversation
- Add RESULT_TESTNAME variable to support unique testcase IDs - Add --lava-testcase-id CLI parameter - Add LAVA_TESTCASE_ID parameter to AudioRecord.yaml - Update Read_me.md with LAVA_TESTCASE_ID documentation Resolves issue qualcomm-linux#378 by ensuring unique testcase IDs in LAVA when running multiple AudioRecord configurations in parallel. Signed-off-by: Teja Swaroop Moida <tmoida@qti.qualcomm.com>
Contributor
Author
|
Here are the details of the validation job: |
bhargav0610
reviewed
Apr 2, 2026
Contributor
bhargav0610
left a comment
bhargav0610
left a comment
There was a problem hiding this comment.
LGTM
is this validated on all Targets ?
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
3 participants
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.
Description
This PR fixes the testcase ID collision issue in LAVA by implementing flexible testcase naming for the AudioRecord test suite, enabling parallel execution of multiple AudioRecord configurations in CI.
Problem
LAVA was experiencing testcase ID collisions because:
AudioRecordin the .res fileAudioRecord_Config01,AudioRecord_Config03, etc. based on the job definitionSolution
Implemented a flexible testcase naming mechanism that allows LAVA to specify unique testcase IDs:
RESULT_TESTNAMEvariable - Defaults toAudioRecordbut can be overridden via CLI parameter--lava-testcase-idparameter - Allows LAVA to specify unique testcase names for each configurationLAVA_TESTCASE_IDYAML parameter - Passes the testcase ID from LAVA job definition to the script$RESULT_TESTNAMEinstead of$TESTNAME--lava-testcase-idensures unique result files even if setup fails