Skip to content

2.4.0 Configuration takes 25s vs 2s with 2.1.0 #1905

Open
0 of 1 issue completed
Open
0 of 1 issue completed
@jonathanlermitage

Description

@jonathanlermitage

What happened?

Disable gradle caching, then run gradlew clean buildPlugin test --scan:

My unit test contains only one simple test case (assertTrue(true);).
If I do not run the tests (gradlew clean buildPlugin --scan), the performance of the configuration phase is good.
Also, I did not have this problem with the first 2.3.1-SNAPSHOTs. We had a discussion about #1836 on Discourse (Feb 28, via a private discussion), then I tested a 2.3.1-SNAPSHOT build. So, I guess I'm impacted by a recent change.

intellijPlatform {
            create("IC", "2024.3.5")
            instrumentationTools() // commented out when using platform plugin 2.4.0
            pluginVerifier()
            testFramework(TestFrameworkType.Platform)
            zipSigner()
        }

withType<Test> {
        dependsOn("prepareSandbox")
        useJUnitPlatform()

        jvmArgs("-Djava.awt.headless=true")

        testLogging {
            exceptionFormat = TestExceptionFormat.FULL
            events.add(TestLogEvent.PASSED)
            events.add(TestLogEvent.FAILED)
            events.add(TestLogEvent.SKIPPED)
            showStandardStreams = true
            showCauses = true
            showExceptions = true
            showStackTraces = true
        }
    }

I did not reproduce with the intellij template plugin.
I can send my project via https://uploads.jetbrains.com/ if needed.

Relevant log output or stack trace

Steps to reproduce

Disable gradle caching, then run gradlew clean buildPlugin test --scan

Gradle IntelliJ Plugin version

2.4.0

Gradle version

8.13

Operating System

Windows

Link to build, i.e. failing GitHub Action job

No response

Sub-issues

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions