fix(wpss_remoteproc): write .res next to test by cd’ing into testcase dir #150
Conversation
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
… dir - Align with other remoteproc tests: use find_test_case_by_name + cd - Ensures ./wpss_remoteproc.res is created under the suite folder so LAVA can pick it up Signed-off-by: Srikanth Muppandam <[email protected]>
vnarapar
approved these changes
Sep 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
LAVA was missing the result because run.sh wrote ./wpss_remoteproc.res from the Runner CWD.
This change mirrors other remoteproc tests by cd’ing into the testcase directory (via find_test_case_by_name)
so the .res is created beside run.sh at suites/Kernel/Baseport/wpss_remoteproc/.
No test logic changes—just reliable result placement and removal of the “Result file missing” warning.