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

Improve v++ logging (HAST-280) #85

Open
sarahelsaig opened this issue Oct 26, 2022 · 0 comments
Open

Improve v++ logging (HAST-280) #85

sarahelsaig opened this issue Oct 26, 2022 · 0 comments

Comments

@sarahelsaig
Copy link
Member

sarahelsaig commented Oct 26, 2022

We don't get a lot of useful information if a Vitis build fails during the v++ compilation, particularly in synthesis. This is because the individual steps of the process are logged separately in deep subfolders inside /tmp/hastlayer/. This makes debugging with the docker image particularly inconvenient. We should at least detect when the main log says please look at the run log file '{path}' for more information and copy that file into the ./App_Data/logs directory for easier availability.

Jira issue

@sarahelsaig sarahelsaig changed the title M Improve v++ logging Oct 26, 2022
@github-actions github-actions bot changed the title Improve v++ logging M (HAST-280) Oct 26, 2022
@sarahelsaig sarahelsaig changed the title M (HAST-280) Improve v++ logging (HAST-280) Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants