-
Notifications
You must be signed in to change notification settings - Fork 177
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
Print details about USC compilation process when running tests #2403
Labels
Comments
cptartur
assigned kkawula, AbdelStark and ddoktorski and unassigned kkawula and AbdelStark
Oct 17, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Nov 14, 2024
<!-- Reference any GitHub issues resolved by this PR --> Towards #2403 ## Introduced changes <!-- A brief description of the changes --> - Keep sierra file path in `TestTargetRaw` so it can be printed later
github-merge-queue bot
pushed a commit
that referenced
this issue
Nov 14, 2024
<!-- Reference any GitHub issues resolved by this PR --> Closes #2403 ## Introduced changes <!-- A brief description of the changes --> - Print information about compiling Sierra as a spinner message - Skip printing the path for unsaved files ## Checklist <!-- Make sure all of these are complete --> - [X] Linked relevant issue - [X] Updated relevant documentation - [X] Added relevant tests - [X] Performed self-review of the code - [X] Added changes to `CHANGELOG.md`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which components does the task require to be changed? (think hard pls)
snforge
Description
Right now it doesn't give any feedback. If USC compilation is long running it might see like a forge problem.
The text was updated successfully, but these errors were encountered: