Sterling Greene

@hcayless I was running into the same thing this weekend. Does #126 seem to fix this?

We've made some changes on the gradle/gradle side so that this doesn't deadlock and just emits deprecation warnings for 5.0. Problems like #255 will still be an issue

@jimshowalter could you give `7.5.1-20220729132837+0000` a try? You can upgrade via: `./gradlew wrapper --gradle-version=7.5.1-20220729132837+0000`

@jimshowalter @Telesphoreo could you give `7.5.1-20220730234330+0000` a try? If this doesn't fix it, could you provide the "Queued nodes" output again for this version? it has some more diagnostics.

Testing with the latest 7.6 with Java 19, everything appears to be working: [builds.gradle.org/viewLog.html?buildId=54959159&buildTypeId=Gradle_Experimental_Check_Stage_ReadyforNightly_Trigger](https://builds.gradle.org/viewLog.html?buildId=54959159&buildTypeId=Gradle_Experimental_Check_Stage_ReadyforNightly_Trigger) what's left to do: - [x] Update compatibility.adoc to say Gradle can run with JDK19 -...

@bot-gradle test this

Obviously, it would be better to rewrite these things to use test suites

@bot-gradle test and merge

@ljacomet we could take a look at this for 7.6, if you'd like.

Thanks @prbprbprb We have an experimental M1-based pipeline I can run this through