exo-test: erroring on EDX

[charlierudolph]

https://circleci.com/gh/Originate/EDX/49

Was working for 0.23.0.alpha.4 and started failing when upgraded to 0.23.0.alpha.5.

@hugobho @alexdavid you ever seen anything like this or have any idea what could be going wrong

[charlierudolph]

This works locally but not on CI. The docker compose file on CI is:

version: "3"
services:
  bank-service:
    build:
      context: /home/circleci/EDX/bank-service
      dockerfile: Dockerfile.dev
    command: bin/test
    container_name: bank-service
    volumes:
    - /home/circleci/EDX/bank-service:/mnt
    links:
    - postgres9.6.4:postgres
    environment:
      DATABASE_NAME: edx
      DATABASE_PASSWORD: mypassword
      DATABASE_USERNAME: myuser
      EXOCOM_HOST: exocom0.26.1
      POSTGRES: postgres
      ROLE: bank-service
    depends_on:
    - postgres9.6.4
  postgres9.6.4:
    image: postgres:9.6.4
    container_name: postgres9.6.4
    ports:
    - 5432:5432
    environment:
      POSTGRES_DB: edx
      POSTGRES_PASSWORD: mypassword
      POSTGRES_USER: myuser

[charlierudolph]

One difference between alpha 4 and 5 was the introduction of the compose project name env variable to allow the use of separate networks in run vs tests.

List of changes: https://github.com/Originate/exosphere/compare/v0.23.0.alpha.4...v0.23.0.alpha.5

[hugoesthere]

I've never seen this error before, certainly not relating to COMPOSE_PROJECT_NAME, docker compose usually gives pretty clear errors related to that. Does this happen consistently?

[charlierudolph]

Consistently on circle. Reran a build of alpha 4 and that passed, so I don't think something on circle changed

[hugoesthere]

What are the rest of the logs? Is this happening within a single docker-compose command or does it happen when we complete one and start another?

[charlierudolph]

The build stalls after this error which appears to be when it attempts to run the first test