TransformationNodeSpec.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix for previous commit.

  1. … 1 more file in changeset.
Fix for previous commit.

  1. … 1 more file in changeset.
Give `ActionNode` and `TransformNode` a common `execute()` method and merge their `NodeExecutor` implementations.

  1. … 12 more files in changeset.
Give `ActionNode` and `TransformNode` a common `execute()` method and merge their `NodeExecutor` implementations.

  1. … 12 more files in changeset.
Decouple work node implementations from projects a little, so that a node is given a context through which it can locate its execution services, rather than using a project service registry directly.

  1. … 20 more files in changeset.
Decouple work node implementations from projects a little, so that a node is given a context through which it can locate its execution services, rather than using a project service registry.

  1. … 20 more files in changeset.
Decouple work node implementations from projects a little, so that a node is given a context through which it can locate its execution services, rather than using a project service registry.

  1. … 20 more files in changeset.
Decouple work node implementations from projects a little, so that a node is given a context through which it can locate its execution services, rather than using a project service registry directly.

  1. … 20 more files in changeset.
Revert "Revert PR #8715 for improving scheduler performance"

Re-introduce the scheduler performance improvements, now

that https://github.com/gradle/gradle/pull/10050 has

been fixed.

This reverts commit 18b6c927b38e48eed57a5db28f9939ceb84de3d4.

  1. … 8 more files in changeset.
Revert "Revert PR #8715 for improving scheduler performance"

Re-introduce the scheduler performance improvements, now

that https://github.com/gradle/gradle/pull/10050 has

been fixed.

This reverts commit 18b6c927b38e48eed57a5db28f9939ceb84de3d4.

  1. … 8 more files in changeset.
Use correct order for Mock expectations

For some reason Groovy 2.5.7 is stricter WRT the order of declared

mock expectations for this particular test. Changing the order to

accurately reflect the true invocation order allows this test to pass

with Groovy 2.5.4 and 2.5.7

Use correct order for Mock expectations

For some reason Groovy 2.5.7 is stricter WRT the order of declared

mock expectations for this particular test. Changing the order to

accurately reflect the true invocation order allows this test to pass

with Groovy 2.5.4 and 2.5.7

Use correct order for Mock expectations

For some reason Groovy 2.5.7 is stricter WRT the order of declared

mock expectations for this particular test. Changing the order to

accurately reflect the true invocation order allows this test to pass

with Groovy 2.5.4 and 2.5.7

Use correct order for Mock expectations

For some reason Groovy 2.5.7 is stricter WRT the order of declared

mock expectations for this particular test. Changing the order to

accurately reflect the true invocation order allows this test to pass

with Groovy 2.5.4 and 2.5.7

Use correct order for Mock expectations

For some reason Groovy 2.5.7 is stricter WRT the order of declared

mock expectations for this particular test. Changing the order to

accurately reflect the true invocation order allows this test to pass

with Groovy 2.5.4 and 2.5.7

Use correct order for Mock expectations

For some reason Groovy 2.5.7 is stricter WRT the order of declared

mock expectations for this particular test. Changing the order to

accurately reflect the true invocation order allows this test to pass

with Groovy 2.5.4 and 2.5.7

Use correct order for Mock expectations

For some reason Groovy 2.5.7 is stricter WRT the order of declared

mock expectations for this particular test. Changing the order to

accurately reflect the true invocation order allows this test to pass

with Groovy 2.5.4 and 2.5.7

Use correct order for Mock expectations

For some reason Groovy 2.5.7 is stricter WRT the order of declared

mock expectations for this particular test. Changing the order to

accurately reflect the true invocation order allows this test to pass

with Groovy 2.5.4 and 2.5.7

TODO

  1. … 8 more files in changeset.
Revert PR #8715 for improving scheduler performance

The changes seem to cause some builds not finishing.

Reverting to see if they are the cause.

  1. … 8 more files in changeset.
Check fewer times if dependencies complete

If a unit of work finishes, only anything which depends on that unit

of work can become ready for execution.

There is the special case of tasks in other builds which do not notify

the current task execution plan when they finish executing. So we need

to keep polling for those.

  1. … 7 more files in changeset.
Check fewer times if dependencies complete

If a unit of work finishes, only anything which depends on that unit

of work can become ready for execution.

There is the special case of tasks in other builds which do not notify

the current task execution plan when they finish executing. So we need

to keep polling for those.

  1. … 7 more files in changeset.
Check fewer times if dependencies complete

If a unit of work finishes, only anything which depends on that unit

of work can become ready for execution.

There is the special case of tasks in other builds which do not notify

the current task execution plan when they finish executing. So we need

to keep polling for those.

  1. … 7 more files in changeset.
Check fewer times if dependencies complete

If a unit of work finishes, only anything which depends on that unit

of work can become ready for execution.

There is the special case of tasks in other builds which do not notify

the current task execution plan when they finish executing. So we need

to keep polling for those.

  1. … 7 more files in changeset.
Check fewer times if dependencies complete

If a unit of work finishes, only anything which depends on that unit

of work can become ready for execution.

There is the special case of tasks in other builds which do not notify

the current task execution plan when they finish executing. So we need

to keep polling for those.

  1. … 7 more files in changeset.
Check fewer times if dependencies complete

If a unit of work finishes, only anything which depends on that unit

of work can become ready for execution.

There is the special case of tasks in other builds which do not notify

the current task execution plan when they finish executing. So we need

to keep polling for those.

  1. … 7 more files in changeset.
Clean up Node.isPublicNode

  1. … 5 more files in changeset.
Do not count action nodes for the progress bar

Those do not have build operations so they won't be substracted and

we end up with something less than 100% at the end.

  1. … 6 more files in changeset.
Schedule isolation as node

Instead of trying to run it ad-hoc

  1. … 7 more files in changeset.
Merge branch 'release'