Stubbing with some AdditionalMatchers can NPE with null actuals

[kidnme]

import static org.hamcrest.MatcherAssert.assertThat;
import static org.hamcrest.Matchers.is;
import static org.mockito.AdditionalMatchers.leq;
import static org.mockito.Matchers.eq;
import static org.mockito.Mockito.mock;
import static org.mockito.Mockito.when;

import org.junit.Test;

public class BlahTest
{
    @Test
    public void test()
    {
        final BoolResult mockBoolResult = mock(BoolResult.class);

        when(mockBoolResult.getResult(eq(5))).thenReturn(true);  // Succeeds as expected
        when(mockBoolResult.getResult(leq(5))).thenReturn(true); // Fails with an NPE - as of v2.0.64 - unexpected!

        assertThat(mockBoolResult.getResult(null), is(false));
    }

    interface BoolResult
    {
        boolean getResult(Integer value);
    }
}

[ChristianSchwarz]

Seems to be related to my removal of HandyReturnValues. I will look into it!
Thanks for reporting! Did you found more Matcher that misbehave like that?

[ChristianSchwarz]

@kidnme
I can't reproduce it with mockito/master [HEAD]. Can you test it with v2.0.71-beta ?
Edit: There is no issue with the matchers but with the implementation of CompareTo.