Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Renable ContinuousBuildCancellationCrossVersionSpec

See https://github.com/gradle/gradle-private/issues/2976

This commit uses a workaround to fix that issue.

    • -0
    • +4
    ./tooling/fixture/ContinuousBuildToolingApiSpecification.groovy
  1. … 1 more file in changeset.
Force AbstractTestDirectoryProvider to use Class (#12431)

Closes https://github.com/gradle/gradle-private/issues/2988

This PR adds `className` to `AbstractTestDirectoryProvider` so there'll be no more `unknown-test-class`.

  1. … 407 more files in changeset.
Improve and document flags for running multi version tests

This commit makes it easier to run all or partial configurations and

properly takes into account using the system property on the command

line.

    • -0
    • +3
    ./tooling/fixture/ToolingApiCompatibilitySuiteRunner.groovy
  1. … 8 more files in changeset.
Increase timeout for ContinuousBuildToolingApiSpecification

Looking at the log, it seems that ContinuousBuildToolingApiSpecification

somehow takes longer than before and starts failing. Increase timeout for now.

    • -2
    • +4
    ./tooling/fixture/ContinuousBuildToolingApiSpecification.groovy
Disable dependency verification when resolving tooling API clients from cross version tests.

    • -0
    • +1
    ./tooling/fixture/ToolingApiDistributionResolver.groovy
Don't run TAPI tests for versions <2.6

These are not supported by Gradle anymore.

    • -2
    • +10
    ./tooling/fixture/ToolingApiCompatibilitySuiteRunner.groovy
Properly isolate tests from the Gradle user home

When running Gradle, we use the current working directory as the

base directory for searching a `settings.gradle` file. For tooling

API tests this working directory is the one of Gradle itself, which

causes a number of issues because the root directory of the project

doesn't match the working directory.

Therefore, Gradle finds the `settings.gradle` file of its own build,

instead of finding the one in the test.

As a workaround, TAPI tests now use an action which will set the

working directory to the test directory, which should cover most

cases. Additional cases like missing settings files in projects

under tests have to be handled separately, as demonstrated in this

commit for the ProjectBuilder test.

    • -0
    • +33
    ./tooling/fixture/SetWorkingDirectoryAction.java
    • -0
    • +13
    ./tooling/fixture/ToolingApi.groovy
  1. … 4 more files in changeset.
Do not notify busy daemons

    • -3
    • +14
    ./tooling/fixture/ToolingApi.groovy
  1. … 4 more files in changeset.
Revert "Merge pull request #10954 from gradle/eskatos/kotlin-dsl/new-tapi-model-in-tooling-api-jar"

This reverts commit 00cdf938c0d9df3786760adeecf9c2e7d45bff78, reversing

changes made to 28d5b62f4ac9b3b57b57c5b625869516198ed836.

    • -2
    • +2
    ./tooling/fixture/ToolingApiAdditionalClasspathProvider.groovy
  1. … 20 more files in changeset.
Let KotlinDslScriptsModel cross version test classload on tapi < 6.0

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -2
    • +2
    ./tooling/fixture/ToolingApiAdditionalClasspathProvider.groovy
  1. … 1 more file in changeset.
Add an outgoing variants report

This commit introduces an `outgoingVariants` task which generates

a report of the outgoing variants of a project. This is useful

for debugging and understanding variant aware resolution.

It becomes possible for a plugin author to understand what variants

are already produced by a project based on the plugins applied, and

what artifacts are attached to what variant.

  1. … 9 more files in changeset.
Merge branch 'master' into lptr/execution/introduce-build-operations

    • -0
    • +21
    ./tooling/fixture/ProgressEvents.groovy
  1. … 1 more file in changeset.
Fix flakiness introduced by #10088

    • -0
    • +21
    ./tooling/fixture/ProgressEvents.groovy
  1. … 1 more file in changeset.
Catch and remember connect exceptions directly in 'withConnection()' #2

See also 05019368445

Bump version to 6.0

  1. … 19 more files in changeset.
Fix some more tests

    • -4
    • +10
    ./tooling/fixture/ProgressEvents.groovy
  1. … 2 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -25
    • +0
    ./tooling/fixture/ContinuousBuildToolingApiSpecification.groovy
  1. … 98 more files in changeset.
Replace 'Matchers' with 'CoreMatchers'

So we do not require 'org.hamcrest:hamcrest-library' as additional

dependency anymore. Which was only available for most of the tests

because it leaked onto the test compile classpath.

    • -3
    • +3
    ./tooling/fixture/ContinuousBuildToolingApiSpecification.groovy
  1. … 162 more files in changeset.
Add missing @Override to all modules

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +8
    ./tooling/fixture/GradleVersionSpec.java
  1. … 999 more files in changeset.
TAPI tests pass ResultHandler as FailureTracker to waitForAllPendingCalls()

    • -1
    • +2
    ./tooling/fixture/TestResultHandler.groovy
  1. … 4 more files in changeset.
Catch and remember connect exceptions directly in 'withConnection()'

This allows us to analysis this exception in the retry conditions

for problems caused by bugs that exist in older Gradle versions.

    • -2
    • +12
    ./tooling/fixture/ToolingApiSpecification.groovy
Move Kotlin DSL TAPI model tests for build scripts as cross-version tests

Signed-off-by: Paul Merlin <paul@gradle.com>

  1. … 3 more files in changeset.
Fix TaskVisibilityCrossVersionSpec

by explicitly making the Kotlin DSL model task trigger an

"invisible implicit task"

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -5
    • +21
    ./tooling/fixture/ToolingApiSpecification.groovy
  1. … 1 more file in changeset.
Fix tapi cross versions tests after new buit-in task

Signed-off-by: Paul Merlin <paul@gradle.com>

Introduce KotlinBuildScriptTemplateModelCrossVersionSpec

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -1
    • +1
    ./tooling/fixture/ToolingApiAdditionalClasspath.groovy
  1. … 2 more files in changeset.
Allow TAPI cross-version tests to inject additional client-side classpath

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +36
    ./tooling/fixture/ToolingApiAdditionalClasspath.groovy
    • -0
    • +31
    ./tooling/fixture/ToolingApiAdditionalClasspathProvider.groovy
Minor refinements in cross-version TAPI fixtures

mostly small edits and a few explaining comments

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -8
    • +12
    ./tooling/fixture/ToolingApiCompatibilitySuiteRunner.groovy
Remove container callback measurement feature toggle

    • -2
    • +0
    ./tooling/fixture/ToolingApiClasspathProvider.groovy
  1. … 7 more files in changeset.
Report transform progress events to TAPI listeners

This commit introduces a new `OperationType.TRANSFORM` and corresponding

TAPI progress events. The `TransformOperationDescriptor` currently only

contains the display names of the transformer and subject.

    • -1
    • +11
    ./tooling/fixture/ProgressEvents.groovy
  1. … 24 more files in changeset.
Track task creation and execution times for listener/config callbacks

Project evaluation listener callbacks such as `afterEvaluate {}` and

configuration callbacks of domain object collections such as `all {}`

are now attributed to the plugin that registered them. Thus, the origin

plugins for tasks created in such callbacks is correctly determined and

their execution times are added to the plugin's total execution time

that is reported to TAPI progress listeners.

    • -0
    • +2
    ./tooling/fixture/ToolingApiClasspathProvider.groovy
  1. … 4 more files in changeset.