[
https://issues.apache.org/jira/browse/JAMES-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282916#comment-17282916
]
ASF GitHub Bot commented on JAMES-3500:
---------------------------------------
chibenwa opened a new pull request #291:
URL: https://github.com/apache/james-project/pull/291
```
07:41:22,949 [INFO] Apache James :: Server :: Web Admin server integration
tests :: Distributed SUCCESS [27:23 min]
07:41:22,945 [INFO] Apache James :: Server :: JMAP (draft) :: RabbitMQ +
Object Store + Cassandra Integration testing SUCCESS [25:27 min]
07:41:22,933 [INFO] Apache James :: Server :: Cassandra with RabbitMQ -
guice injection SUCCESS [26:34 min]
07:41:22,877 [INFO] Apache James :: Mailbox :: Cassandra ...............
SUCCESS [24:50 min]
07:41:22,893 [INFO] Apache James MPT Imap Mailbox - Cassandra ..........
SUCCESS [15:46 min]
07:41:22,947 [INFO] Apache James :: Server :: JMAP RFC-8621 :: Distributed
Integration Testing SUCCESS [15:17 min]
07:41:22,930 [INFO] Apache James :: Server :: Cassandra - guice injection
SUCCESS [11:41 min]
07:41:22,950 [INFO]
------------------------------------------------------------------------
07:41:22,950 [INFO] BUILD SUCCESS
07:41:22,951 [INFO]
------------------------------------------------------------------------
07:41:22,951 [INFO] Total time: 04:37 h
07:41:22,951 [INFO] Finished at: 2021-02-11T07:41:22Z
07:41:22,952 [INFO]
------------------------------------------------------------------------
```
6 projects takes more than 15 minutes to test.
Looking deeper, they do not use forks. Hence each test class will:
- Initialize testContainers
- Rebuild the custom Cassandra image
- Start its own containers (no reuse across forks is possible due to
testcontiner lifecycle management)
- Starts a not warm James, with not yet efficient JIT - slowing down the
startup of the first test up to a factor 10.
All of that leads to a time waste of several minutes per test class.
I believe huge gains can be made by leveraging fork reuse - as we did in the
past. Please note that I dropped the fork count where relevant - we likely gain
way more with fork reuse.
----------------------------------------------------------------
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]
