Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Revert removal of org.gradle.util.Clock

The change currently breaks the build scan plugin.

    • -1
    • +0
Avoid using Gradle internal class to calculate elapsed time

Also suggest using --offline for poor remote build cache connections

Fix imports

Rename variable for accuracy

Fix BeanDynamicObject performance

The withNoImplementsMissing and withNoProperties methods were

unnecessarily creating new objects when the current one already

satisfied the condition. They also created an ad-hoc sublcass when

the booleans in the class already carried all the necessary information.

Remove misc deprecated classes and methods in core module (#1755)

  1. … 4 more files in changeset.
Make Path more efficient

The segments in paths are very repetitive (e.g. core:integTest, ide:integTest, ...),

so interning them compacts their memory usage quite a bit. In order to benefit more

from that, we should use `Path` instead of `String` in more places.

Introduce convenience methods on worker lease service

Introduce convenience methods on worker lease service

  1. … 8 more files in changeset.
Build elapsed time summary (#1689)

* Indicate Gradle's continued progress in the format `3h 23m 2s`

* Improve AntLoggingAdapterTest to avoid flaky test

Merge pull request #1711 from gradle/dd-parallel-downloads

Parallel download of artifacts

Remove TODO we'll never do

Update release notes and docs about --offline

+review REVIEW-6496

    • -4
    • +5
Merge branch 'release'

    • -0
    • +4
Allow nested usage of BuildOperationProcessor

Use a dynamically sized thread pool in BuildOperationProcessor to allow

nested usage. Maximum in-flight work is managed by worker leases, the

size of that thread pool has nothing to do with that. It being caped

at maxWorkers made it impossible to use BuildOperationProcessor inside

a work enqueued to BuildOperationProcessor up to a certain degree. This

commit fixes that.

Add build operation for resolving all artifacts

This generates a "resolve artifacts" build operation if

getFiles() is called on lenient configuration.

Refine ParallelTestExecutionIntegrationTest

The forkEvery value didn’t make sense for some maxWorkers/maxParallelForks values under test

Shouldn’t be flaky anymore

Exercise more potential deadlock situations, see the two previous commits

Remove items from release notes that already part of 3.5

    • -48
    • +0
Fix potential deadlock on parallel test execution again

Follow up on c9799ad, see its message for details

This commits invert the worker lease holder test processor and the

max n parallel test processor, putting the former before the later.

Given that the “max n parallel test” processor uses non-blocking proxy

actors, a deadlock could happen when forkEvery=1.

This was discovered while working on ParallelTestExecutionIntegrationTest


Fix BlockingHttpServer.CyclicBarrierAnyOfRequestHandler fixture

Simplify handler code

Prevent missing test failures despite assertions failures on Jetty threads

Prevent race conditions caused by missing locking and wrong ordering

Adjust expectations to name change of config project build operation

Fix mock setup for new service

Make reusable build operation details static

Simplify configure project operation name calculation

Use dependency injection getter to access service

Preserve the exact message text when wrapping as unchecked exception

If the message is the one presented to the user in the summary,

it should not be polluted with additional information. The build

operation executor now uses this wrapping behavior.

Add new service to integration test setups

Remove `println` from tests

Remove unused class