Vladimir Sitnikov

See https://github.com/jqwik-team/jqwik/actions/runs/9609449124/job/26503957069#step:5:253 > e: '-Xjdk-release=8' option is not supported by used JDK: C:\hostedtoolcache\windows\Java_Zulu_jdk\8.0.412-8\x64 Ideally, I would suggest using a recent JDK (e.g. Java 17) for the build purpose via JDK...

I guess something wrong went with cache restoration. I'll look into that later. Apparently, PRs with failing CI jobs are not mergeable.

I'm adding toolchains to Apache JMeter (see https://github.com/apache/jmeter/pull/5989), and it turns out there's a need for configuring several Java versions: 1) Java for build purposes 2) Java for test purposes...

> I think it would make sense if the OS/JDK used for compilation was the one I use for release versions Imagine something like * 3 jobs: macos, windows, linux...

I tried re-enabling shrink for my action chain, and it turns out to spend too much time shrinking (too many variations? too many restrictions in the current shrink approach like...

Apache Calcite has expression simplifier. Here's a typical hand-crafted test: https://github.com/apache/calcite/blob/b9c2099ea92a575084b55a206efc5dd341c0df62/core/src/test/java/org/apache/calcite/rex/RexProgramTest.java#L1826-L1836 ```java @Test void testSimplifyEqOrIsNullAndEqSame() { // (deptno = 10 OR deptno IS NULL) AND deptno = 10 // ==>...

Probably a slightly better term would be `serializer`. In other words, it serializes Java objects to `Java source` or `Kotlin source` formats.

In any case, stacktrace without streams is way easier to read

I agree shortening the stacktrace does not really solve the root cause.

I'm afraid it boils down to `.shrink()` must not be called "after the state has been modified" when action accesses state. In other words, it is similar to https://github.com/jlink/jqwik/pull/427, however,...