Spock fails with insufficient invocation count when route cause was underneath exception

Assuming we use groovy and assuming we have such service method:

method(input){ Long val = Optional.ofNullable(input).map(Integer::longValue).orElse(doesntmatter);
return otherService.something(val);
}

Also assuming we expect that second service Mock will be invoked once (1 * otherService...).
When passing Long as "input" parameter i would expect exception:

java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.Integer

But what i get is failed invocation count for otherService shadowing underneath exception.

Removing count check results in correct behaviour - exception being properly handled.

For me it looks like Spock completely ignores underneath exceptions in case of failed invocation count checks.

Start with a minimal Groovy specification using an interaction count check and the service method described in the issue, then inspect how failed invocation counts and underlying exceptions are handled. Done means the ClassCastException is reported instead of being hidden by the insufficient invocation count failure.