Bump Gradle to 8.0.2

[snazy]

No description provided.

[snazy]

Hope this PR is rather "boring" ;)

[snazy]

Weird test failures. Rebased + ran some of these tests locally (passed fine).

[quarkus-bot]

Failing Jobs - Building ebe6573

Status	Name	Step	Failures	Logs	Raw logs
✔️	Gradle Tests - JDK 11
⌛	Gradle Tests - JDK 11 Windows	Build	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✔️	JVM Tests - JDK 17
✖	JVM Tests - JDK 17 Windows	Build	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 19
✖	Maven Tests - JDK 11	Build	Failures	Logs	Raw logs
✖	Maven Tests - JDK 11 Windows	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Gradle Tests - JDK 11 Windows #

📦 integration-tests/gradle

✖ io.quarkus.gradle.devmode.MultiSourceProjectDevModeTest.main line 22 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeTestUtils that uses java.util.function.Supplier, java.util.function.Supplierjava.util.concurrent.atomic.AtomicReference, java.util.concurrent.atomic.AtomicReferencejava.lang.String, java.lang.Stringboolean was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

---

⚙️ JVM Tests - JDK 17 Windows #

- Failing: extensions/vertx/deployment 
! Skipped: extensions/agroal/deployment extensions/amazon-lambda-http/deployment extensions/amazon-lambda-rest/deployment and 362 more

📦 extensions/vertx/deployment

✖ io.quarkus.vertx.mdc.VertxMDCTest.mdc line 144 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: expected: <10> but was: <0>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)

✖ io.quarkus.vertx.mdc.VertxMDCTest.mdcNonVertxThreadTest line 121 - More details - Source on GitHub

java.lang.AssertionError: 

Expected: a collection containing "Test MDC value ### Test 1"

---

⚙️ Maven Tests - JDK 11 #

- Failing: integration-tests/maven 

📦 integration-tests/maven

✖ io.quarkus.maven.it.DevMojoIT.testThatTheTestsAreReRunMultiModule - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Failed to wait for test run4 TestStatus{lastRun=4, running=4, testsRun=2, testsPassed=1, testsFailed=1, testsSkipped=0}
	at io.quarkus.maven.it.continuoustesting.ContinuousTestingMavenTestUtils.waitForNextCompletion(ContinuousTestingMavenTestUtils.java:74)
	at io.quarkus.maven.it.LaunchMojoTestBase.testThatTheTestsAreReRunMultiModule(LaunchMojoTestBase.java:67)

✖ io.quarkus.maven.it.DevMojoIT.testThatTheTestsAreReRunMultiModule - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Failed to wait for test run4 TestStatus{lastRun=4, running=4, testsRun=2, testsPassed=1, testsFailed=1, testsSkipped=0}
	at io.quarkus.maven.it.continuoustesting.ContinuousTestingMavenTestUtils.waitForNextCompletion(ContinuousTestingMavenTestUtils.java:74)
	at io.quarkus.maven.it.LaunchMojoTestBase.testThatTheTestsAreReRunMultiModule(LaunchMojoTestBase.java:67)

---

⚙️ Maven Tests - JDK 11 Windows #

- Failing: integration-tests/maven 

📦 integration-tests/maven

✖ io.quarkus.maven.it.DevMojoIT.testThatTheTestsAreReRunMultiModule - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Failed to wait for test run3 TestStatus{lastRun=2, running=3, testsRun=2, testsPassed=0, testsFailed=1, testsSkipped=0}
	at io.quarkus.maven.it.continuoustesting.ContinuousTestingMavenTestUtils.waitForNextCompletion(ContinuousTestingMavenTestUtils.java:74)
	at io.quarkus.maven.it.LaunchMojoTestBase.testThatTheTestsAreReRunMultiModule(LaunchMojoTestBase.java:63)

✖ io.quarkus.maven.it.DevMojoIT.testThatTheApplicationIsReloadedMultiModule line 611 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Failed to wait for test run3 TestStatus{lastRun=2, running=3, testsRun=2, testsPassed=0, testsFailed=1, testsSkipped=0}
	at io.quarkus.maven.it.continuoustesting.ContinuousTestingMavenTestUtils.waitForNextCompletion(ContinuousTestingMavenTestUtils.java:74)
	at io.quarkus.maven.it.DevMojoIT.testThatTheApplicationIsReloadedMultiModule(DevMojoIT.java:611)

✖ io.quarkus.maven.it.DevMojoIT.testThatTheTestsAreReRunMultiModule - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Failed to wait for test run3 TestStatus{lastRun=2, running=3, testsRun=2, testsPassed=0, testsFailed=1, testsSkipped=0}
	at io.quarkus.maven.it.continuoustesting.ContinuousTestingMavenTestUtils.waitForNextCompletion(ContinuousTestingMavenTestUtils.java:74)
	at io.quarkus.maven.it.LaunchMojoTestBase.testThatTheTestsAreReRunMultiModule(LaunchMojoTestBase.java:63)

✖ io.quarkus.maven.it.DevMojoIT.testThatTheApplicationIsReloadedMultiModule line 611 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Failed to wait for test run3 TestStatus{lastRun=2, running=3, testsRun=2, testsPassed=0, testsFailed=1, testsSkipped=0}
	at io.quarkus.maven.it.continuoustesting.ContinuousTestingMavenTestUtils.waitForNextCompletion(ContinuousTestingMavenTestUtils.java:74)
	at io.quarkus.maven.it.DevMojoIT.testThatTheApplicationIsReloadedMultiModule(DevMojoIT.java:611)

[aloubyansky]

There still seem to be issues on Windows.

[gsmet]

The Gradle tests have been unstable on Windows for a while. We have a memory issue I think. @snazy if at some point you could have a look that would be awesome.