On 14/03/2019 19:26, Igal Sapir wrote: > Does test.threads default to 1 for a reason?
Mostly historical. The tests weren't originally designed to run in parallel. > If there is no objection, I would like to set the default to the number > of available CPU Threads. It looks like that can be done with a custom > Ant task which should be fairly simple to implement. I over-ride it locally so I'm not going to be directly affected. A custom Ant task seems a little over-engineered compared to setting a property in build.properties. I do wonder about CI systems. It is potentially a big change that might take someone by surprise. We'll need to update some buildbot configuration for example. I have visions of a CI system with lots of cores running lots of builds in parallel suddenly grinding to a halt because a Tomcat build suddenly tries to use every CPU. But I don't know now likely that is. I guess I'm -0. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
