Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Gradle integration tests: tackle (Windows) CI issues #32571

Merged
merged 13 commits into from
Apr 15, 2023
Merged

Gradle integration tests: tackle (Windows) CI issues #32571

merged 13 commits into from
Apr 15, 2023

Commits on Apr 14, 2023

  1. Bump Gradle from 8.0.2 to 8.1

    @snazy
    snazy committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    07e6cbe View commit details
    Browse the repository at this point in the history

  2. Minor configuration-cache related fix for buildNative

    @snazy
    snazy committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    3c2a8c4 View commit details
    Browse the repository at this point in the history

  3. Fix test-project "test resources vs main resources" 

    The test-project for `TestResourcesVsMainResourcesTest` did not work with "recent Quarkus versions", see `integration-tests/gradle/src/main/resources/test-resources-vs-main-resources/src/main/java/org/acme/Config.java` (was still using `io.quarkus.arc.config.ConfigProperties`, failed to compile, but the IT didn't fail.)
    @snazy
    snazy committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    a05d523 View commit details
    Browse the repository at this point in the history

  4. Add a system property to forcefully limit the heap size of Quarkus' G… 

    …radle worker processes
    @snazy
    snazy committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    dfd5206 View commit details
    Browse the repository at this point in the history

  5. Fix property for the Gradle Daemon idle timeout

    @snazy
    snazy committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    b421c8f View commit details
    Browse the repository at this point in the history

  6. Limit heap size for Gradle daemons, force some code related system pr… 

    …operties
    @snazy
    snazy committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    b70569d View commit details
    Browse the repository at this point in the history

  7. Increase CI timeout for Gradle jobs from 80 to 120 minutes (Windows j… 

    …ob takes about 70 minutes to succeed)
    @snazy
    snazy committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    4b0d845 View commit details
    Browse the repository at this point in the history

  8. Allow running Gradle ITs in IntelliJ (JAVA_HOME's not set by default)

    @snazy
    snazy committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    c37644d View commit details
    Browse the repository at this point in the history

  9. Fail Gradle ITs that expect no error (and vice versa) according to Gr… 

    …adle exit code
    @snazy
    snazy committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    92fdf8c View commit details
    Browse the repository at this point in the history

  10. Programmatically disable some Gradle features in ITs

    @snazy
    snazy committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    bf5a675 View commit details
    Browse the repository at this point in the history

  11. Correct JDK-19 -> 20 exclusions (Gradle 8.1)

    @snazy
    snazy committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    ccf168a View commit details
    Browse the repository at this point in the history

  12. Increase dev-mode timeout on Windows to 90 seconds

    @snazy
    snazy committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    cc8b86b View commit details
    Browse the repository at this point in the history

  13. Gradle integration tests: tackle CI issues / final changes 

    The major issue was (very likely) that in the `Gradle Tests - JDK 11 Windows` CI job (at least) the Quarkus process running in dev-mode somehow "survived". The observed pattern is that one dev-mode test ran successfully and all following dev-mode tests failed with test timeout exceptions (awaitability). Adding some code to collect the `List` of child `ProcessHandle`s before calling `ProcessHandle.destroy()` plus a (potentially over-cautious) `ProcessHandle.destroyForcibly()` seems to solve the Gradle-Windows-CI issue. A couple of CI runs did not fail.

This change adds "process dumps" (not really useful w/ Windows :( ) from before and after the test run to the failed test outputs.
    @snazy
    snazy committed Apr 14, 2023
    Configuration menu
    Copy the full SHA
    32f74e0 View commit details
    Browse the repository at this point in the history