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
Use TestFixturesPlugin to Run Minio in Tests (#37852) #38973
Conversation
Pinging @elastic/es-distributed |
* Use TestFixturesPlugin to Run Minio in Tests * Closes elastic#37680 * Closes elastic#37783
bf9219d
to
6fb6847
Compare
run elasticsearch-ci/1 |
1 similar comment
run elasticsearch-ci/1 |
run elasticsearch-ci/1 |
doesn't look like this backported cleanly. can check next week |
* Disable Minio fixture and tests that require it when fixtures are disabled or Docker is not available * Relates elastic#37852
oh, ok. I've merge that into here so we find out. thank you @original-brownbear! |
run elasticsearch-ci/1 |
@original-brownbear I might need help here... 😄 I included the PR you mentioned, and it fails in the same way |
@talevy sure, will take a look tomorrow :) |
description = "Runs REST tests using the Minio repository." | ||
} | ||
|
||
preProcessFixture.dependsOn(writeDockerFile) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@atorok you may be able to help here better than me :) Is there anything different about this task in 6.6
maybe that would prevent this way of triggering the docker file write from working? It seems this task isn't executed before composeUp
and thus composeUp
fails.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't usually back port build changes this far so I'm fairly sure there's some change to the plugin missing in this branch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yea that makes sense, I guess we could just make composeUp
depend on writeDockerFile
as a workaround in 6.6
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@talevy ah sorry missed your ping. Yea but I remember there was some weirdness around this actually happening before fixes by Alpar => let's try triggering on composeUp
:)
thank you for the help Armin. to be honest, I haven't been keeping up with build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, since we don't have any production code changes here + the failure is def. still a possibility I think it's fine to go ahead with this still
thanks Armin! I'll run the tests again just to add more confidence |
run elasticsearch-ci/1 |
Use TestFixturesPlugin to Run Minio in Tests
Closes [CI] minio fails due to port clashes #37680
Closes Use TestFixturesPlugin to Spin up Minio in S3 Plugin Tests #37783
backport of #37852