fixed exec syntax, it needs a command not only strings#118
Merged
Conversation
speriaswamy-amd
requested changes
Apr 9, 2026
- it fixes the following run-time error
[err] bash: line 1: Starting: command not found
Signed-off-by: Ahsan Kabir <Ahsan.Kabir@amd.com>
speriaswamy-amd
approved these changes
Apr 10, 2026
ahskabir
force-pushed
the
bugfix/cmdsyntax
branch
from
07278ab to
3a4b697
Compare
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
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.
[err] bash: line 1: Starting: command not found
Motivation
CVS exec command syntax is wrong without this fix
Technical Details
exec was given only string but a command must exists
Test Plan
This error was revealed while running perftest. The error is non-fatal.
Test Result
With this fix, bash error command will not be seen in the log
Submission Checklist