ci(test): CI test regularly dies with "Pool is closed" #823
Assignees
Labels
Comments
|
We also tried #819 which should help. Let's keep pushing on that direction? |
BYK
changed the title
BYK
added a commit
that referenced
this issue
Jan 19, 2021
Fixes #823. In `install.sh` we build a local sentry image that is used by many services from using the build context under the `./sentry` directory. To avoid building this image multiple times, we also give it a specific name which is referred from multiple services. The issue is, we also run `docker-compose build --parallel` which creates a race condition when building this image as `docker-compose` doesn't check whether the image is already there or not. This is the root cause of all these random failures: an unsurprising race condition.
BYK
added a commit
that referenced
this issue
Jan 19, 2021
Fixes #823. In `install.sh` we build a local sentry image that is used by many services from using the build context under the `./sentry` directory. To avoid building this image multiple times, we also give it a specific name which is referred from multiple services. The issue is, we also run `docker-compose build --parallel` which creates a race condition when building this image as `docker-compose` doesn't check whether the image is already there or not. This is the root cause of all these random failures: an unsurprising race condition.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Attempted to fix in #768, etc. Still not resolved.
The text was updated successfully, but these errors were encountered: