Skip to content
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

[Bug] PERUSE and OUT files do not always work in Jenkins/SSH #79

Open
rsbeckerca opened this issue Sep 29, 2021 · 1 comment
Open

[Bug] PERUSE and OUT files do not always work in Jenkins/SSH #79

rsbeckerca opened this issue Sep 29, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@rsbeckerca
Copy link
Member

Describe the bug
Make-started processes do not always get their output to Jenkins/SSH

To Reproduce

  1. Put a recipe in containing either a compiler or PERUSE. A sample is PERUSE/IN $NULL/;ll
  2. Run this.
  3. See error

Expected behavior
PERUSE and compilers should be able to see the SSH output file. We need either a fix or workaround.

NonStop

  • OS: Yes
  • Version All of them
@rsbeckerca rsbeckerca added the bug Something isn't working label Sep 29, 2021
@rsbeckerca
Copy link
Member Author

It should be noted that when gtacl is used to run PERUSE, the output is successfully sent to SSH. This appears to be something specific to GMAKE that we should be able to address - perhaps by locating the correct terminal being used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant