-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[CI] minio fails due to port clashes #37680
Comments
Pinging @elastic/es-core-infra |
We don't yet run this part in parallel. Right now, that would imply creating a minio-fixture simmilar to |
Looks like another failure on the 6.x line:
|
* Retry starting Minio five times in case we run into a race between finding the free port and starting it up * Closes elastic#37680
* Retry starting Minio five times in case we run into a race between finding the free port and starting it up * Closes #37680
Reopening this as it's still failing with the current solution, I'm on it fixing it for good in #37783 now though. |
* Closes elastic#37680 * Closes elastic#37783
New occurrence for
|
Fix is incoming for |
* Use TestFixturesPlugin to Run Minio in Tests * Closes elastic#37680 * Closes elastic#37783
Fixed in 6.x via 4b6678f |
* Use TestFixturesPlugin to Run Minio in Tests * Closes elastic#37680 * Closes elastic#37783
* Use TestFixturesPlugin to Run Minio in Tests (#37852) * Use TestFixturesPlugin to Run Minio in Tests * Closes #37680 * Closes #37783 * Fix S3 Repository ITs When Docker is not Available (#37878) * Disable Minio fixture and tests that require it when fixtures are disabled or Docker is not available * Relates #37852 * add explicit composeUp dependsOn
Looks like minio is failing again due to clashes with already opened port.
This seems to have been already handled through
#32701 and #32208 but it still occurred in master.
For example:
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/1411/console
It doesn't seem like the port is hardcoded:
elasticsearch/plugins/repository-s3/build.gradle
Line 205 in 7394892
Maybe it's a race condition when gradle runs in parallel?
The text was updated successfully, but these errors were encountered: