docker-compose log dumps when verbose #288
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 tasks
tzaffi
commented
May 23, 2023
tzaffi
commented
May 23, 2023
tzaffi
commented
May 23, 2023
1 task
tzaffi
commented
May 23, 2023
bbroder-algo
approved these changes
May 23, 2023
tzaffi
commented
May 23, 2023
This was referenced May 23, 2023
1 task
Eric-Warehime
approved these changes
May 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
To improve visibility of C.I. build failures, utilize new logging capabilities in the sandbox (algorand/sandbox#181) when
VERBOSE_HARNESS=1.In particular under verbose, we can now see:
docker compose upcommanddocker-compose logsfor:TODO
.envbefore merging