ltp: correctly fetch LTPROOT #88
Merged
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
LTPROOT was previously fetched via --env option, but after the introduction of the new LTPFramework implementation, this feature stopped to work. This patch brings back the correct usage of it. Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
acerv
force-pushed
the
fix_ltproot_env
branch
from
51eba60 to
12342d7
Compare
Member
|
Reviewed-by: Li Wang liwang@redhat.com |
wangli5665
approved these changes
Jan 15, 2026
Member
|
Maybe release a bugfix release (v3.2.1 or v3.3) + update in LTP before new release? Or do we want more testing? |
Member
|
I see you already have suggested the same thing on LTP ML, thank you! |
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.
LTPROOT was previously fetched via --env option, but after the introduction of the new LTPFramework implementation, this feature stopped to work. This patch brings back the correct usage of it.
Signed-off-by: Andrea Cervesato andrea.cervesato@suse.com
Reviewed-by: Li Wang liwang@redhat.com