BuildOperationExecutorIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

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

    • -2
    • +2
    ./BuildOperationExecutorIntegrationTest.groovy
  1. … 872 more files in changeset.
Annotate integ tests failing with instant execution in :baseServices

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

    • -0
    • +2
    ./BuildOperationExecutorIntegrationTest.groovy
Annotate integ tests failing with instant execution in :baseServices

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

    • -0
    • +2
    ./BuildOperationExecutorIntegrationTest.groovy
Annotate integ tests failing with instant execution in :baseServices

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

    • -0
    • +2
    ./BuildOperationExecutorIntegrationTest.groovy
Make paths/names of included builds immutable (#10998)

Changes the “build path” for included builds to be determined at inclusion time based on the directory name, or a user supplied override. Previously, we tried to use the root project name defined in the included build. This caused a lot of complexity due to it not being known until part way through building the included build.

This change also disallows use of `buildSrc` as a project name, as it collides with the `buildSrc` nested build.

    • -0
    • +1
    ./BuildOperationExecutorIntegrationTest.groovy
  1. … 72 more files in changeset.
Fix test

    • -0
    • +1
    ./BuildOperationExecutorIntegrationTest.groovy
Fix tests

    • -1
    • +1
    ./BuildOperationExecutorIntegrationTest.groovy
Rework task logger build id decoration

    • -1
    • +1
    ./BuildOperationExecutorIntegrationTest.groovy
  1. … 7 more files in changeset.
Decorate task logger with build operation id so usage from external thread is linked to correct task

    • -1
    • +1
    ./BuildOperationExecutorIntegrationTest.groovy
  1. … 3 more files in changeset.
Decorate task logger with build operation id so usage from external thread is linked to correct task

    • -1
    • +1
    ./BuildOperationExecutorIntegrationTest.groovy
  1. … 3 more files in changeset.
Decorate task logger with build operation id so usage from external thread is linked to correct task

    • -1
    • +1
    ./BuildOperationExecutorIntegrationTest.groovy
  1. … 3 more files in changeset.
spelling: enqueuing

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

Signed-off-by: Bo Zhang <bo@gradle.com>

    • -1
    • +1
    ./BuildOperationExecutorIntegrationTest.groovy
  1. … 1 more file in changeset.
Rationalise handling of “current” build operation and build operation ID

For an upcoming change to emit console logging as build operation progress events, we need to associate all progress logging with the build operation. This pulled a thread on some long overdue cleanup.

The end result is:

1. Base build operation infrastructure is consolidated org.gradle.internal.operations.

2. Mechanism for passing thread global current build operation is more test friendly, and better named.

3. A consistent mechanism is used for binding the current operation to the thread, instead of two mechanisms.

4. Build operation IDs are typed to OperationIdentifier.

There is no public API or user behaviour change.

    • -1
    • +1
    ./BuildOperationExecutorIntegrationTest.groovy
  1. … 147 more files in changeset.
Change test to run two successive builds using the GradleBuild task

This test was endangered to be flaky. Running two builds in a row,

there is never a guarantee that they will run on the same daemon.

    • -4
    • +11
    ./BuildOperationExecutorIntegrationTest.groovy
Clarify that only builds started by a GradleBuild task cause the issue

    • -2
    • +2
    ./BuildOperationExecutorIntegrationTest.groovy
Add tests for: build operation ids are unique for nested builds

#2622

    • -0
    • +97
    ./BuildOperationExecutorIntegrationTest.groovy
  1. … 3 more files in changeset.