-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shell-test does not appear to work on VxWorks #939
Comments
Although this is a "bug" - since shell functionality is typically disabled by default it is not clear how much of a priority this is. In the default config the shell function returns |
I think I have a idea of what's going on here.... |
The shell may add extra output beyond the intended content, but the shell-test was only looking for exact match. Extra output may include whitespace and/or an echo of the command itself. This reworks the shell test to allow for this extra output, as long as the intended string appears in the content of the file it will pass.
The shell may add extra output beyond the intended content, but the shell-test was only looking for exact match. Extra output may include whitespace and/or an echo of the command itself. This reworks the shell test to allow for this extra output, as long as the intended string appears in the content of the file it will pass.
Fix nasa#56, Refactor CDS to use generic pool implementation
Describe the bug
The "shell-test" program attempts to run the following command:
But this does not appear to work correctly on VxWorks 6.9. The test reports:
To Reproduce
Enable shell and run "shell-test" on MCP750
Expected behavior
Test should pass
System observed on:
MCP750 VxWorks 6.9
Additional context
I'm not familiar enough with VxWorks, it seems the interactive shell does not even have an "echo" command so I am not sure how this is expected to work to begin with.
If run directly on the shell as a test, I get:
So it is not clear to me how this is expected to work.
Reporter Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: