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

Documentation build does not show errors when it fails #623

Closed
3 tasks done
jphickey opened this issue Nov 30, 2022 · 0 comments · Fixed by #625
Closed
3 tasks done

Documentation build does not show errors when it fails #623

jphickey opened this issue Nov 30, 2022 · 0 comments · Fixed by #625
Assignees

Comments

@jphickey
Copy link
Contributor

Checklist (Please check before submitting)

  • I reviewed the Contributing Guide.
  • I reviewed the cFS README.md file to see if the feature is in the major future work.
  • I performed a cursory search to see if the feature request is relevant, not redundant, nor in conflict with other tickets.

Is your feature request related to a problem? Please describe.
When using the workflow in build-deploy-doc.yml, if the "Build Document" step fails, then the job stops there. However, the stderr output was redirected to a file, which is not uploaded as an artifact until the next step. Therefore, it is not possible to see what actually failed by looking at the log, because the information is in a file that is never displayed nor uploaded.

Describe the solution you'd like
Show the stderr output on the console so it can be seen even if artifacts are not uploaded.

Additional context
Adjusting the redirection should solve this.

Requester Info
Joseph Hickey, Vantage Systems, Inc.

@jphickey jphickey self-assigned this Nov 30, 2022
dzbaker added a commit that referenced this issue Dec 6, 2022
Fix #623, show stderr output on doc build workflow
@dzbaker dzbaker closed this as completed in 0466572 Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant