Maven Tests on JDK 11 Windows get stuck for 3.2 branch

[rsvoboda]

Describe the bug

Maven Tests on JDK 11 Windows gets stuck with Results:Terminate batch job (Y/N)? for 3.2 branch

See the timestamps on last two lines, there is 8 minutes nothing before termination:

Noticed in #36697 execution

Windows are the most used OS by users with enabled build time metrics.
This makes backports and CI failures investigation more painful and can hide other issues.
This needs to be investigated and fixed.

CI on main seems to pass, I have seen green light on #36752
Quarkus CI / Maven Tests - JDK 11 Windows (pull_request) Successful in 16m Details

Expected behavior

Maven Tests on JDK 11 Windows pass

Actual behavior

Maven Tests on JDK 11 Windows gets stuck

How to Reproduce?

Do something similar to #36697

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @quarkusio/devtools (maven)

[rsvoboda]

Looking again into the log and I think the job hit timeout-minutes: 80 as defined in https://github.com/quarkusio/quarkus/blob/3.2/.github/workflows/ci-actions-incremental.yml#L352

Upstream is using 130 minutes timeout introduced in https://github.com/quarkusio/quarkus/blob/main/.github/workflows/ci-actions-incremental.yml#L400 together with dev mode inclusion
ut even before that change, timeout was set to 100 minutes.

CC @aloubyansky

[rsvoboda]

#35132 increased the timeouts including windows tests, I think we should backport that one, added backport label to it.

[geoand]

I assume we can close this since we no longer support JDK 11

[rsvoboda]

JDK 11 is supported on 3.2 branch, but this can be closed because:

• Some longer timeouts for CI #35132 was backported to 3.2 branch so
• Last PR in 3.2 branch ([3.2] Do not record local sources in runtime config defaults #40077) was fully green

[geoand]

👌