Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix Guava performance regression

Since 24.1, Guava included a change that made ImmutableSet.Builder with unspecified expected size allocate a lot more memory for many items. We haven't bumped into this problem before, because we used the Android variant of Guava that somehow didn't contain the regressing change. With moving to the Java 8 variant we now have to deal with this problem.

Fix Guava performance regression

Since 24.1, Guava included a change that made ImmutableSet.Builder with unspecified expected size allocate a lot more memory for many items. We haven't bumped into this problem before, because we used the Android variant of Guava that somehow didn't contain the regressing change. With moving to the Java 8 variant we now have to deal with this problem.

Fix Guava performance regression

Since 24.1, Guava included a change that made ImmutableSet.Builder with unspecified expected size allocate a lot more memory for many items. We haven't bumped into this problem before, because we used the Android variant of Guava that somehow didn't contain the regressing change. With moving to the Java 8 variant we now have to deal with this problem.

See https://github.com/google/guava/issues/3223 for more details.

Address some review comments

WIP

Revert "Merge pull request #8991 from gradle/lptr/core/use-guava-java-8"

This reverts commit b3c791db65d344ddbe1878b56db41761db385aa5, reversing

changes made to 29c75bff79d89cfd6f69335a6bd056f1bdf1d160.

  1. … 11 more files in changeset.
add message

Update released version to latest snapshot

Update library versions in build init to latest for 5.6

Update version to 5.6

Merge remote-tracking branch 'origin/master-test' into release-test

Fail configuration phase deliberately

Fail configuration phase deliberately

Mark known flaky performance test in report (#8997)

This closes https://github.com/gradle/gradle-private/issues/1735

We want to mark the known performance test scenarios in the report even when they pass. This can give us insights of how the scenarios work previously. In this way, we can easily know, "this scenario fails, ah, it's marked as flaky", or, "this scenario is improved, but hold on, it's marked as flaky, let's not rebaseline it".

Publish 5.4-20190412010826+0000

Remove cpu temp

Remove cpu temp

Remove pid

Remove pid

Update

Update

Command line performance test

    • binary
    /commons-math3-3.6.1.jar
    • -0
    • +9
    /pid-instrumentation.gradle
Command line performance test

Fix `instant execution for multi-level subproject` flaky assertion

when run with --parallel

by asserting on the grouped task output

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

Merge pull request #8991 from gradle/lptr/core/use-guava-java-8

Use Java 8-compatible variant of Guava

Remove Gradle Wrapper version output from user manual (#9000)

* Remove Gradle Wrapper version output from user manual

It would take far too much effort to ensure that the sample in the Gradle

Wrapper reference chapter that shows the output of running `./gradlew -v`

is consistent with the current version of Gradle. Since it doesn't provide

a lot of value to the reader, I've just removed it.

Fix failed tests

Query known invalid failures only once

Instead of querying Github each time when searching an invalid failure.

Query known invalid failures only once

Instead of querying Github each time when searching an invalid failure.

Query known invalid failures only once

Instead of querying Github each time when searching an invalid failure.