Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add integration test coverage for shared resources

Signed-off-by: Mark Vieira <portugee@gmail.com>

    • -0
    • +64
    ./ParallelTaskExecutionIntegrationTest.groovy
Check for already registered model in TaskContainer

A ModelMap<Task> is a shadow version of the TaskContainer inside the

software model. Although difficult, it is possible to create an element

in ModelMap<Task> before creating the same element in TaskContainer.

This creates a duplicate instance that, in some case, cause both

instance to be used in the task graph causing issues.

    • -0
    • +35
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 1 more file in changeset.
Check for already registered model in TaskContainer

A ModelMap<Task> is a shadow version of the TaskContainer inside the

software model. Although difficult, it is possible to create an element

in ModelMap<Task> before creating the same element in TaskContainer.

This creates a duplicate instance that, in some case, cause both

instance to be used in the task graph causing issues.

    • -0
    • +35
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 1 more file in changeset.
Check for already registered model in TaskContainer

A ModelMap<Task> is a shadow version of the TaskContainer inside the

software model. Although difficult, it is possible to create an element

in ModelMap<Task> before creating the same element in TaskContainer.

This creates a duplicate instance that, in some case, cause both

instance to be used in the task graph causing issues.

    • -0
    • +35
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 1 more file in changeset.
Check for already registered model in TaskContainer

A ModelMap<Task> is a shadow version of the TaskContainer inside the

software model. Although difficult, it is possible to create an element

in ModelMap<Task> before creating the same element in TaskContainer.

This creates a duplicate instance that, in some case, cause both

instance to be used in the task graph causing issues.

    • -0
    • +35
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 1 more file in changeset.
Fix execution of integration tests

    • -1
    • +1
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 25 more files in changeset.
Fix execution of integration tests

    • -1
    • +1
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 25 more files in changeset.
Fix execution of integration tests

    • -1
    • +1
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 25 more files in changeset.
Fix execution of integration tests

    • -1
    • +1
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 25 more files in changeset.
Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

The `TestFixturesPlugin` of our build has been simplified to leverage the native

test fixtures capabilities. Some noticeable changes:

- the `testFixtures` extension has been replaced with regular dependency declaration

- dependencies on test fixtures are now declared using the `testFixtures` keyword

- test fixtures properly declare an API and an implementation, meaning that the

implementation dependencies of test fixtures no longer leak into the compile

classpath of consumers (in particular tests)

    • -1
    • +1
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 88 more files in changeset.
Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

The `TestFixturesPlugin` of our build has been simplified to leverage the native

test fixtures capabilities. Some noticeable changes:

- the `testFixtures` extension has been replaced with regular dependency declaration

- dependencies on test fixtures are now declared using the `testFixtures` keyword

- test fixtures properly declare an API and an implementation, meaning that the

implementation dependencies of test fixtures no longer leak into the compile

classpath of consumers (in particular tests)

    • -1
    • +1
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 88 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.

    • -1
    • +1
    ./RuleTaskCreationIntegrationTest.groovy
    • -1
    • +1
    ./RuleTaskExecutionIntegrationTest.groovy
  1. … 49 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.

    • -1
    • +1
    ./RuleTaskCreationIntegrationTest.groovy
    • -1
    • +1
    ./RuleTaskExecutionIntegrationTest.groovy
  1. … 97 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.

    • -1
    • +1
    ./RuleTaskCreationIntegrationTest.groovy
    • -1
    • +1
    ./RuleTaskExecutionIntegrationTest.groovy
  1. … 97 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.

    • -1
    • +1
    ./RuleTaskCreationIntegrationTest.groovy
    • -1
    • +1
    ./RuleTaskExecutionIntegrationTest.groovy
  1. … 49 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.

    • -1
    • +1
    ./RuleTaskCreationIntegrationTest.groovy
    • -1
    • +1
    ./RuleTaskExecutionIntegrationTest.groovy
  1. … 97 more files in changeset.
Fix integ tests after new buit-in task

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

    • -1
    • +1
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 3 more files in changeset.
Fix integration tests that relied on placeholder behavior

    • -58
    • +1
    ./RuleTaskBridgingIntegrationTest.groovy
    • -4
    • +10
    ./RuleTaskExecutionIntegrationTest.groovy
  1. … 6 more files in changeset.
Expect errors in tests to appear durign task execution

We are not evaluating the properties during task graph build time now.

    • -1
    • +1
    ./ParallelTaskExecutionIntegrationTest.groovy
  1. … 2 more files in changeset.
Introduce TaskDestroyables.register()

This deprecates the `file()` and `files()` methods we had previously. Also, the getter for files has been moved to the internal API.

    • -7
    • +7
    ./ParallelTaskExecutionIntegrationTest.groovy
  1. … 10 more files in changeset.
Adjust test which used a task name that is now invalid

    • -3
    • +13
    ./RuleTaskCreationIntegrationTest.groovy
Fix issue with enforced tasks and task graph exception

Fixes issue #2407 where an exception thrown while walking a task

graph with a finalizer can cause the build to hang.

    • -0
    • +31
    ./ParallelTaskExecutionIntegrationTest.groovy
  1. … 3 more files in changeset.
Tweaked the API of `BlockingHttpServer` to make it somewhat more convenient to use in tests.

    • -31
    • +31
    ./ParallelTaskExecutionIntegrationTest.groovy
  1. … 15 more files in changeset.
Remove checks for @destroys logging output as it's not guaranteed to occur

    • -20
    • +2
    ./ParallelTaskExecutionIntegrationTest.groovy
More test coverage for destroys annotation

    • -0
    • +48
    ./ParallelTaskExecutionIntegrationTest.groovy
  1. … 1 more file in changeset.
Rename destroys to destroyables and add incubating annotations

    • -5
    • +5
    ./ParallelTaskExecutionIntegrationTest.groovy
  1. … 17 more files in changeset.
Always include a contextual 'cannot determine dependencies for task' error message when the dependencies of a task cannot be calculated. Sometimes this was not included in the logging output.

    • -1
    • +2
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 4 more files in changeset.
Basic support for no-isolation workers

    • -0
    • +2
    ./ParallelTaskExecutionIntegrationTest.groovy
  1. … 15 more files in changeset.
Simplified test case.

    • -17
    • +6
    ./ParallelTaskExecutionIntegrationTest.groovy
Basic support for @Destroys annotation

    • -0
    • +123
    ./ParallelTaskExecutionIntegrationTest.groovy
  1. … 16 more files in changeset.