arrow-core: speedup 'Arb.string()' related slow tests

[abendt]

Some of the tests in arrow-core run slow on the non jvm platforms (#2908)

One reason seems to be the use of Arb.string() especially when used inside arbs that generate collections (map, list, nonemptylist)

See

• let Mapk 'zipN with nullable' tests use Arb.map2 to generate values #2999 (comment)
• let Mapk 'zipN with nullable' tests use Arb.map2 to generate values #2999 (comment)

This MR replaces Arb.string() with Arb.int() in some tests to speed up the execution time

[abendt]

Before https://scans.gradle.com/s/ogbwpswsaig4q/tests/overview

After https://scans.gradle.com/s/i6grm52lc7v6u/tests/overview

[nomisRev]

Wow that is an amazing improvements 😍 Thank you for digging into this @abendt!

A bit related, but also unrelated to this. I am a bit curious if running the tests on latest JDK would increase build times as well. IIRC only building the binaries in the publish step need to run in JDK 11? Related tweet, https://twitter.com/EsaFirm/status/1641083869083602944?s=20

[nomisRev]

Looks awesome @abendt. Just two small nits (probably missing proper imports, so suggestions is going to break).

[abendt]

A bit related, but also unrelated to this. I am a bit curious if running the tests on latest JDK would increase build times as well. IIRC only building the binaries in the publish step need to run in JDK 11? Related tweet, https://twitter.com/EsaFirm/status/1641083869083602944?s=20

Sure, that could prohably improve build times. More ideas:

• gradle configuration takes a long time because of one of the gradle plugins. This makes it very painful to run tests in IntelliJ. You can also see that in the build scan: https://scans.gradle.com/s/i6grm52lc7v6u/performance/configuration. I had to comment out the plugin locally (https://github.com/arrow-kt/arrow/blob/main/build.gradle.kts#L34)
• In other projects i have used the gradle build cache with good results

[serras]

Sure, that could prohably improve build times. More ideas:

• gradle configuration takes a long time because of one of the gradle plugins. This makes it very painful to run tests in IntelliJ. You can also see that in the build scan: https://scans.gradle.com/s/i6grm52lc7v6u/performance/configuration. I had to comment out the plugin locally (https://github.com/arrow-kt/arrow/blob/main/build.gradle.kts#L34)

We actually are working on improving that in #2988, although we may fix it once and for all in the Gradle plug-in we use arrow-kt/arrow-gradle-config#69

[franciscodr]

Thanks for helping us improve the build times, @abendt I appreciate the time you're putting on this!