-
Notifications
You must be signed in to change notification settings - Fork 290
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
Build 151 failed #87
Comments
dartartem
added a commit
to dartartem/eventuate-tram-examples-customers-and-orders
that referenced
this issue
Apr 5, 2021
cer
added a commit
that referenced
this issue
Apr 10, 2021
#87: Build 151 failed. Fixed by incrementing timeout in snapshot tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Build https://app.circleci.com/pipelines/github/eventuate-tram/eventuate-tram-examples-customers-and-orders/151/workflows/2a8c7505-7ed5-4108-a5e9-b1b7c845a629/jobs/651/steps failed
Reason: build-and-test-snapshots.sh failed
*Reason: Failed io.eventuate.examples.tram.ordersandcustomers.snapshottests.SnapshotTest testCustomers
**Reason: I/O error on GET request for "http://localhost:8084/customers": Connection refused (Connection refused); nested exception is java.net.ConnectException: Connection refused (Connection refused)
***Reason: docker-compose failed to start eventuate-tram-examples-customers-and-orders_order-history-text-search-service_2
****Reason: ERROR: for eventuate-tram-examples-customers-and-orders_order-history-text-search-service_2 Cannot start service order-history-text-search-service: driver failed programming external connectivity on endpoint eventuate-tram-examples-customers-and-orders_order-history-text-search-service_2 (0a3fca82cb3f008c791cb248399a5dfa7b15c30f38e70bc8ccbba1b0621cf112): Bind for 0.0.0.0:8084 failed: port is already allocated
*****Reason: there is already eventuate-tram-examples-customers-and-orders_order-history-text-search-service_1
******Reason: order-history-text-search-service starts by ordersTest and customersTest. ordersTest executed first. It tried to start order-history-text-search-service, which depends on elastic search, and while elastic search is pulled, order-history-text-search-service started timeout is elapsed. So, customersTest started creating order-history-text-search-service concurrently
Solution: Increase timeouts start elastic search before order-history-text-search-service
The text was updated successfully, but these errors were encountered: