Ashley

Regarding the module errors you posted in those screenshots, I guess you will need to add the JVM flags at https://github.com/mockito/mockito/blob/main/subprojects/errorprone/errorprone.gradle#L20 to your test runner configuration in IntelliJ. Failing that,...

Think so. I believe you should get a reports directory in one of the `build/` directories that tells you what ran. You can test it by breaking your test locally...

oh is that the retry test? Think that just reruns failed tests to deflake them

This issue also affects another area, which I have put a PR up for at #86. Might be worth considering both PRs together if they are approved and considered for...

Can also reproduce. Think the tool possibly needs to be updated to ignore invalid dates if at all possible to avoid this breaking builds immediately, although the database also needs...

Looks like this also fails on non-final classes when we use the inline mockmaker. Disabling inline mockmaker entirely resolves the issue.

On further investigation, this appears to affect the version of OpenJDK 17 distributed on Dockerhub also. Will remove GraalVM out of the title since this is not GraalVM-specific. ```dockerfile FROM...

Any updates on this? Currently this is blocking us from using Mockito on JDK 17, as we need the inline mockmaker for other internals.

When I ran this, I ran it on the standard OpenJDK provided on the Arch User Repository as well as with Graal. I will recheck this when I have some...

> Closing this as "not reproducible" for now, as we are successfully building on JDK 17. Let us know if you can reproduce this issue specifically with JDK 17. This...