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
[circleci] retry docker-compose testnet startup #872
Conversation
/canary |
Forge run: https://circleci.com/gh/aptos-labs/aptos-core/15390 |
☀️ Canary successful |
/land here goes |
Forge run: https://circleci.com/gh/aptos-labs/aptos-core/15494 |
💔 Test Failed - build-test-deploy |
/land fixed typescript lint woo |
Forge run: https://circleci.com/gh/aptos-labs/aptos-core/15602 |
💔 Test Failed - build-test-deploy |
/land |
❗ Land has been canceled due to this PR being updated with new commits. Please issue another Land command if you want to requeue this PR. |
/land |
💔 Test Failed - build-test-deploy |
/land |
Forge run: https://circleci.com/gh/aptos-labs/aptos-core/15754 |
Docker-compose networking is a bit flaky on CircleCI machines (tracking in a separate issue). Introduce some retry logic to the startup step, blocking for a maximum of 5 minutes.
Resolves #788 for ecosystem tests. Forge improvements coming separately as well :)
Test locally and by canary. To roll this out, we can enable
DOCKER_COMPOSE_BLOCKING
again, to start testing ecosystem stuff that relies on docker-compose.