On 10/07/2019 09:13, Stefan Seelmann wrote:
On 7/9/19 6:13 PM, Emmanuel Lécharny wrote:
On 09/07/2019 17:03, Stefan Seelmann wrote:
Ok, reverted. Let's first see how tests on Jenkins look like, then
ignore if required.
Seems to be required, inn [1] it failed with timeout twice, once on
On 7/9/19 6:13 PM, Emmanuel Lécharny wrote:
>
> On 09/07/2019 17:03, Stefan Seelmann wrote:
>> Ok, reverted. Let's first see how tests on Jenkins look like, then
>> ignore if required.
Seems to be required, inn [1] it failed with timeout twice, once on
Linux Java 12 and once on Windows Java 8.
On 09/07/2019 17:03, Stefan Seelmann wrote:
Ok, reverted. Let's first see how tests on Jenkins look like, then
ignore if required.
Okie. We can also rename the class adding a 'Perf' at the end : it will
then only be ran when you use the 'perf' profile.
Or maybe we should add a special
Ok, reverted. Let's first see how tests on Jenkins look like, then
ignore if required.
On 7/9/19 5:00 PM, Emmanuel Lécharny wrote:
> Hi Stefan,
>
> setting the number of loops down to 100 instead of 1000 will make the
> test successful. The idea was to have enough element so that the cache
>
Hi Stefan,
setting the number of loops down to 100 instead of 1000 will make the
test successful. The idea was to have enough element so that the cache
would break, and it's only failing when the number of added element grow
to > 650.
I suggest we simply @Ignore this test.
On 09/07/2019
