On Sun, 15 May 2016 20:48:22 +0200, Gilles wrote:
Hi.
On Sat, 14 May 2016 15:05:54 -0500, Matt Sicker wrote:
3. Hardware bugs? Rare but possible.
The behaviour is the same on two different machines.
As it is blocking MATH-1341, I can do one the following:
1. annotate the test with "@Ignore"
Hi.
On Sat, 14 May 2016 15:05:54 -0500, Matt Sicker wrote:
3. Hardware bugs? Rare but possible.
The behaviour is the same on two different machines.
As it is blocking MATH-1341, I can do one the following:
1. annotate the test with "@Ignore"
2. find a seed that will make the test pass
3. remo
3. Hardware bugs? Rare but possible.
On 14 May 2016 at 08:01, Gilles wrote:
> On Sat, 14 May 2016 02:47:18 +0200, Gilles wrote:
>
>> Hello.
>>
>> Test method "testNaNsFixedTiesRandom" (in the above unit test class)
>> can pass or fail depending on the seed value.
>>
>> When seed is 1000, the tes
On Sat, 14 May 2016 02:47:18 +0200, Gilles wrote:
Hello.
Test method "testNaNsFixedTiesRandom" (in the above unit test class)
can pass or fail depending on the seed value.
When seed is 1000, the test passes.
When seed is 1001, this failure occurs:
Elements at index 1 differ. expected = 3.0 o
Hello.
Test method "testNaNsFixedTiesRandom" (in the above unit test class)
can pass or fail depending on the seed value.
When seed is 1000, the test passes.
When seed is 1001, this failure occurs:
Elements at index 1 differ. expected = 3.0 observed = 4.0
Elements at index 4 differ. expecte
