You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: