Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Use unified timestamp when cleaning stale data

This fixes https://github.com/gradle/gradle-private/issues/2701

Previously we saw some failures when cleaning stale data. This might be

cause by different timestamps used. This commit uses same timestamp to

clean both testOperation and testExecution table.

Use unified timestamp when cleaning stale data

Previously we saw some failures when cleaning stale data. This might be

cause by different timestamps used. This commit uses same timestamp to

clean both testOperation and testExecution table.

Remove workarounds for Vintage engine

The workaround was unnecessary since `vintageDynamicMethodName` always

returned `null` and we can then simply check the class name from the

ClassSource.

Remove workarounds for Vintage engine

The workaround was unnecessary since `vintageDynamicMethodName` always

returned `null` and we can then simply check the class name from the

ClassSource.

Remove workarounds for Vintage engine

The workaround was unnecessary since `vintageDynamicMethodName` always

returned `null` and we can then simply check the class name from the

ClassSource.

Remove workarounds for Vintage engine

The workaround was unnecessary since `vintageDynamicMethodName` always

returned `null` and we can then simply check the class name from the

ClassSource.

Remove workarounds for Vintage engine

The workaround was unnecessary since `vintageDynamicMethodName` always

returned `null` and we can then simply check the class name from the

ClassSource.

Fix executing Specs tests via JUnit Platform and Vintage engine

Prior to this commit, the JUnitPlatformTestExecutionListener parsed the

unique ID to determine the class and method name for TestIdentifiers

without children but with a ClassSource. This occurs when a Spock test

class uses `@Unroll` on all its test methods. However, other testing

frameworks such as Specs2 don't provide a unique ID that is parseable

which lead to the methodName being null which cause a failure during

serialization. The effect was that tests hung because the build VM

was waiting for the worker to finish the tests it started.

The Spock-specific workaround in our listener is now replaced with a

more robust one that always uses the methodName provided by the JUnit

Platform instead of parsing it.

Fix executing Specs tests via JUnit Platform and Vintage engine

Prior to this commit, the JUnitPlatformTestExecutionListener parsed the

unique ID to determine the class and method name for TestIdentifiers

without children but with a ClassSource. This occurs when a Spock test

class uses `@Unroll` on all its test methods. However, other testing

frameworks such as Specs2 don't provide a unique ID that is parseable

which lead to the methodName being null which cause a failure during

serialization. The effect was that tests hung because the build VM

was waiting for the worker to finish the tests it started.

The Spock-specific workaround in our listener is now replaced with a

more robust one that always uses the methodName provided by the JUnit

Platform instead of parsing it.

Fix executing Specs tests via JUnit Platform and Vintage engine

Prior to this commit, the JUnitPlatformTestExecutionListener parsed the

unique ID to determine the class and method name for TestIdentifiers

without children but with a ClassSource. This occurs when a Spock test

class uses `@Unroll` on all its test methods. However, other testing

frameworks such as Specs2 don't provide a unique ID that is parseable

which lead to the methodName being null which cause a failure during

serialization. The effect was that tests hung because the build VM

was waiting for the worker to finish the tests it started.

The Spock-specific workaround in our listener is now replaced with a

more robust one that always uses the methodName provided by the JUnit

Platform instead of parsing it.

Fix executing Specs tests via JUnit Platform and Vintage engine

Prior to this commit, the JUnitPlatformTestExecutionListener parsed the

unique ID to determine the class and method name for TestIdentifiers

without children but with a ClassSource. This occurs when a Spock test

class uses `@Unroll` on all its test methods. However, other testing

frameworks such as Specs2 don't provide a unique ID that is parseable

which lead to the methodName being null which cause a failure during

serialization. The effect was that tests hung because the build VM

was waiting for the worker to finish the tests it started.

The Spock-specific workaround in our listener is now replaced with a

more robust one that always uses the methodName provided by the JUnit

Platform instead of parsing it.

Upgrade instant-execution tested AGP to latest nightly

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

Upgrade latest smoke tested AGP to 3.6.0-alpha10

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

Use decorated parameters in tests

Use decorated parameters in tests

Update subprojects/docs/src/docs/userguide/java_testing.adoc

Co-Authored-By: Sterling Greene <big-guy@users.noreply.github.com>

Disable some HTTPS tests on JDK 12

Until https://bugs.openjdk.java.net/browse/JDK-8219658 is fixed.

Simplify deferred test project handling

Note that the only difference here is that the deferred functional

tests now are tagged with the stage they are deferred from, not with

the one they are deferred to. We can fix this later (or never).

Simplify deferred test project handling

Note that the only difference here is that the deferred functional

tests now are tagged with the stage they are deferred from, not with

the one they are deferred to. We can fix this later (or never).

Remember build types in stage project

instead of re-calculating them in `StagePasses`

    • -49
    • +65
    /.teamcity/Gradle_Check/projects/StageProject.kt
Fix TeamCity DSL tests

Update released version to latest snapshot

Update library versions in build init to latest for 6.1

Clean release notes and welcome message for 6.1

    • -115
    • +3
    /subprojects/docs/src/docs/release/notes.md
Clean accepted API changes

Update version to 6.1

Publish 5.6.2-20190915230223+0000

Only link to GitHub docs

Recognize contributor

    • -0
    • +7
    /subprojects/docs/src/docs/release/notes.md
Merge remote-tracking branch 'origin/sg/merges/pr-9585'

* origin/sg/merges/pr-9585:

GitAttributesGenerator enhancements

gradle init creates .gitattributes #9583