-
Notifications
You must be signed in to change notification settings - Fork 0
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
quieten down docker #425
quieten down docker #425
Conversation
docker compose --file dev/docker-scripts/four-nodes.yaml down 2> /dev/null | ||
docker compose --file dev/docker-scripts/one-node-no-tss.yaml down 2> /dev/null | ||
./dev/bin/spin-down.sh four-nodes | ||
./dev/bin/spin-down.sh one-node-no-tss |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this works, but it adds a call docker compose --file "$FILE" logs
🤷
dev/bin/spin-up.sh
Outdated
spin_up() { | ||
docker compose --file "$FILE" "$@" up --detach | ||
|
||
if [ $? -ne 0 ]; then | ||
echo "Error: 'docker compose up' failed." | ||
echo "Retrying verbose:" | ||
docker compose --file "$FILE" up --detach | ||
fi | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This assumes docker is good and exits with an exit code if it hit any problems...
@frankiebee can review at leisure |
Frankie is gonna test how this behaves in CI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks good to me, but you my still want @frankiebee's sign off too
note: i'll get a screen shot of ci failing in a different branch then i'll approve and merge if i like it |
@frankiebee here's the branch where you see it failing: #431 |
Our tests are pretty spammy with docker spinning up / down.
This makes it a lot easier to see where "actual" tests are up to, and also for us to see that there is still logging coming out of substrate.