Fix MailServiceBeanIT #11478
Merged
Fix MailServiceBeanIT #11478
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…1472 Without pinning down the port, sometimes Testcontainers thinks it should apply the waiting strategy on the SMTP port. Telling it explicitely which port to use fixes this.
poikilotherm
added
Component: Code Infrastructure
Contributor
|
Integration tests passing - merging. |
github-project-automation
bot
moved this from QA ✅
to Merged 🚀
in IQSS Dataverse Project
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Without pinning down the port, sometimes Testcontainers thinks it should apply the waiting strategy on the SMTP port. Telling it explicitely which port to use fixes this.
Which issue(s) this PR closes:
Special notes for your reviewer:
None
Suggestions on how to test this:
Watch the integration tests not fail in CI
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Nope
Is there a release notes update needed for this change?:
Nope
Additional documentation:
Nope