Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'master' into westline/services

Merge branch 'release'

Fix jacoco flaky test (#11166)

This fixes https://github.com/gradle/build-tool-flaky-tests/issues/2

Previously jacocoTestReport task seems to be executed before test task,

which results in sporadical errors. This PR fixes it by explicitly

making jacocoTestReport depend on test task.

Fix regexp for checking error message (#11167)

Fix regexp for checking error message

Fix regexp for checking error message

Test executor number can now go into two digits as well.

Fixes gradle/build-tool-flaky-tests#8

Merge pull request #11161 from gradle/eskatos/ie/filetree-sourcetask

Let instant execution support more FileTree and SourceTask use cases

Remove unused import

Ensure that managed task properties that were not initialized prior to serialization can be used after deserialization.

Remove some unnecessary in-memory caching from the "lenient" instantiation scheme. This caching duplicates the caching that already happens in the class generator.

Publish 6.0-20191029000116+0000

Change instant execution serialization to handle abstract model types.

Reuse the approach used to serialize the state of abstract task types.

Change the implementation of `DeserializationInstantiator` so that services and other Gradle-provided state is injected into the instances it creates, to match the state that is injected into the instances created by the `Instantiator` for the same instantiation scheme.

Fix formatting of angle brackets in javadoc

Fail when applying the java plugin on top of platform

Previously, this would only log a deprecation warning. With 6.0 this is

finally an error, in the same way that applying the `java-platform`

plugin on top of the `java` one is already.

Fixes #11162

Workaround for localhost lookup JDK bug (for 6.0) (#11153)

Workaround for localhost lookup JDK bug (for 6.0)

Merge pull request #11154 from gradle/wolfs/incremental/test-nested-domain-collection

Add test for nested domain object containers as input

Remove licenses plugin from santaTrackerAndroidBuild

    • -2
    • +4
    /subprojects/performance/templates.gradle
Merge branch 'release'

Increase timeout in integration test

Since these tests test unstable Gradle processes, they alway have

to spin up their own daemons. If the tests run in an environment short

on resources - for example if they run with several other tests in

parallel - starting up the daemon can take longer. Thus we allow

the tests to wait for up to 2 minutes now.

Set 'org.gradle.workers.max' to 'maxParallelForks' on CI (#11158)

We now also have situations were two or more integration test tasks

run in parallel. We want to limit the total amount of test workers

that run in parallel to reduce flakiness caused by too many Gradle

daemon processes running in parallel.

Remove broken import

Remove unused utility test configurations (#11155)

I created these configs two years ago for some testing. They haven't

been used since then. Now that everything is maintained in the TC

config DSL, these two configurations should either be better linked

to everything else (there is a lot duplication with other configurations

in the Check pipeline) or removed. I think they can be removed.

Add test for nested domain object containers as input

Merge branch 'release'

Increase integration test timeout

Fixes gradle/build-tool-flaky-tests#1

Increase timeout in integration test

This test runs several build in parallel and thus spins up multiple

daemons. If the test runs in an environment short on resources -

for example if it runs with several other tests in parallel - starting

up all the daemons can take longer. Thus we allow the test to wait for

up to 2 minutes now.

Fixes: https://github.com/gradle/build-tool-flaky-tests/issues/14

Increase timeout in integration test

This test runs several build in parallel and thus spins up multiple

daemons. If the test runs in an environment short on resources -

for example if it runs with several other tests in parallel - starting

up all the daemons can take longer. Thus we allow the test to wait for

up to 2 minutes now.

Fixes: https://github.com/gradle/build-tool-flaky-tests/issues/14

Increase timeout in integration test

Since this tests an unstable/broken Gradle process, it alway has

to spin up its own daemon. If the test runs in an environment short

on resources - for example if it runs with several other tests in

parallel - starting up the daemon can take longer. Thus we allow

the test to wait for up to 2 minutes now.

Fixes: https://github.com/gradle/build-tool-flaky-tests/issues/10

Increase timeout in integration test

Since this tests an unstable/broken Gradle process, it alway has

to spin up its own daemon. If the test runs in an environment short

on resources - for example if it runs with several other tests in

parallel - starting up the daemon can take longer. Thus we allow

the test to wait for up to 2 minutes now.

Fixes: https://github.com/gradle/build-tool-flaky-tests/issues/10

Use `hostname` on macOS to lookup local host name

This is to work around a five second lag when using the JDK approach, see https://bugs.openjdk.java.net/browse/JDK-8143378.