[
https://issues.apache.org/jira/browse/JAMES-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17283776#comment-17283776
]
ASF GitHub Bot commented on JAMES-3500:
---------------------------------------
jeantil commented on a change in pull request #293:
URL: https://github.com/apache/james-project/pull/293#discussion_r575312925
##########
File path:
server/mailet/mock-smtp-server/src/main/java/org/apache/james/mock/smtp/server/testing/MockSmtpServerExtension.java
##########
@@ -43,7 +44,8 @@
DockerMockSmtp() {
mockSmtpServer = DockerContainer.fromName(Images.MOCK_SMTP_SERVER)
- .withLogConsumer(outputFrame -> LOGGER.debug("MockSMTP: " +
outputFrame.getUtf8String()));
+ .withLogConsumer(outputFrame -> LOGGER.debug("MockSMTP: " +
outputFrame.getUtf8String()))
+ .waitingFor(Wait.forLogMessage(".*Mock SMTP server started.*",
1));
Review comment:
that's weird:
https://github.com/testcontainers/testcontainers-java/blob/17b4f6c136f6f2c7dc223bad407221f62a8f0088/core/src/main/java/org/testcontainers/containers/wait/strategy/HostPortWaitStrategy.java#L26
seems to use `getLivenessCheckPorts` (with an `s`) for the external checks and
https://github.com/testcontainers/testcontainers-java/blob/17b4f6c136f6f2c7dc223bad407221f62a8f0088/core/src/main/java/org/testcontainers/containers/wait/strategy/HostPortWaitStrategy.java#L35
uses `getExposedPorts` for the internal checks and before suggesting this I
checked that this was already the case in 1.15.1
I don't see how you could use the container if both ports are not exposed
since the tests call both the smtp and the http service ...
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Fasten the build
> ----------------
>
> Key: JAMES-3500
> URL: https://issues.apache.org/jira/browse/JAMES-3500
> Project: James Server
> Issue Type: Improvement
> Components: Build System
> Reporter: Benoit Tellier
> Priority: Major
>
> On master, stable tests takes 5h16 and unstable tests takes 1h51
> Deploy (whatever it means took 1h05)
> Total, this took 8h+
> I can not be productive while waiting a full work-day for a build result, and
> I believe I am not the only one in that case.
> I would like to help reduce the total build time down to (say) 3 hours.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
