Chris,
On Sat, Mar 16, 2019 at 8:22 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Igal,
>
> On 3/15/19 22:38, Igal Sapir wrote:
> > Chris,
> >
> > On Fri, Mar 15, 2019 at 4:56 PM Christopher Schultz <
> > ch...@christophersch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Igal,
On 3/15/19 22:38, Igal Sapir wrote:
> Chris,
>
> On Fri, Mar 15, 2019 at 4:56 PM Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Igal,
>>
>> On 3/15/19 16:45, Igal Sa
Chris,
On Fri, Mar 15, 2019 at 4:56 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Igal,
>
> On 3/15/19 16:45, Igal Sapir wrote:
> >
> > I looked deeper into build.xml and I found some interesting
> > information and a simple
Chris,
On Fri, Mar 15, 2019 at 4:53 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
>
>
> I think you are on Windows (?),. but maybe you could use this script:
>
> https://github.com/ChristopherSchultz/apache-tomcat-stuff/tree/master/bi
> n
>
> (look for test-tomcat-release.sh)
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Igal,
On 3/15/19 16:45, Igal Sapir wrote:
> On Fri, Mar 15, 2019 at 9:45 AM Konstantin Kolinko
> wrote:
>
>> чт, 14 мар. 2019 г. в 22:26, Igal Sapir :
>> What is the use case? People verifying a release? CI
>> servers that may have different har
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Igal,
On 3/14/19 16:29, Igal Sapir wrote:
> On 3/14/2019 12:51 PM, Mark Thomas wrote:
>> 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
On Fri, Mar 15, 2019 at 9:45 AM Konstantin Kolinko
wrote:
> чт, 14 мар. 2019 г. в 22:26, Igal Sapir :
>
> What is the use case? People verifying a release? CI servers that may
> have different hardware?
>
The idea was more for testing new releases. On my laptop setting
test.threads to 8 comple
чт, 14 мар. 2019 г. в 22:26, Igal Sapir :
>
> Does test.threads default to 1 for a reason?
>
> 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.
It
On 3/14/2019 12:51 PM, Mark Thomas wrote:
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 T
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
Does test.threads default to 1 for a reason?
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.
Best,
Igal
11 matches
Mail list logo