You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by GitBox <gi...@apache.org> on 2022/04/24 09:49:31 UTC
[GitHub] [qpid-jms] CAIWan1998 opened a new pull request, #47: Run all the tests in multiple forked VM
CAIWan1998 opened a new pull request, #47:
URL: https://github.com/apache/qpid-jms/pull/47
Maven will run all tests in a single forked VM by default. This can be problematic if there are a lot of tests or some very memory-hungry ones. We can fork more test VM by setting `<fork>1.5C</fork>`.
=====================
If there are any inappropriate modifications in this PR, please give me a reply and I will change them.
--
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.
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[GitHub] [qpid-jms] gemmellr commented on pull request #47: Run all the tests in multiple forked VM
Posted by GitBox <gi...@apache.org>.
gemmellr commented on PR #47:
URL: https://github.com/apache/qpid-jms/pull/47#issuecomment-1108330617
The change proposed of using 1.5C forkCount by default is not one we will be making, for a variety of reasons such as:
- Mostly that the tests wont necessarily all handle it, and as the various CI failures shows, they dont.
- Test consistency.
- More JVMs will often mean more memory being used, not less.
- More JVMs means mores threads, as does more tests, probably slowing things down in lower resource envs like CI, rather than speeding them up.
- The overall run not being all that long currently.
Running all the tests in parallel requires that all the tests have explicitly been written with that in mind, and that everything they do/use is able to handle it. Whilst many will work just fine, particularly the pure unit tests, some of the tests or things they used invariably will not as they simply arent written to cater for it, particularly in the system testing.
--
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.
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org