Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Let `InstantExecutionJacocoInteg*Test` run on JDK14 or earlier only

    • -0
    • +3
    ./org/gradle/util/TestPrecondition.groovy
  1. … 1 more file in changeset.
[WiP] Explicitly declare different Gradle distributions for testing

    • -1
    • +1
    ./org/gradle/util/TestPrecondition.groovy
  1. … 234 more files in changeset.
[WiP] Explicitly declare different Gradle distributions for testing

    • -1
    • +1
    ./org/gradle/util/TestPrecondition.groovy
  1. … 234 more files in changeset.
[WiP] Explicitly declare different Gradle distributions for testing

    • -1
    • +1
    ./org/gradle/util/TestPrecondition.groovy
  1. … 222 more files in changeset.
[WiP] Explicitly declare different Gradle distributions for testing

    • -1
    • +1
    ./org/gradle/util/TestPrecondition.groovy
  1. … 234 more files in changeset.
[WiP] Explicitly declare different Gradle distributions for testing

    • -1
    • +1
    ./org/gradle/util/TestPrecondition.groovy
  1. … 225 more files in changeset.
[WiP] Explicitly declare different Gradle distributions for testing

    • -1
    • +1
    ./org/gradle/util/TestPrecondition.groovy
  1. … 226 more files in changeset.
Add support for test `@DisplayName` (#13250)

If @DisplayName annotation is attached, output the value to test result XML.

* Recognize contributor

* Add missing `@UsedByScanPlugin` annotations

Co-authored-by: Daiki Hirabayashi <hirabayashi@infoscience.co.jp>

Co-authored-by: Daiki Hirabayashi <gigabowser@hotmail.co.jp>

Signed-off-by: Daiki Hirabayashi <hirabayashi@infoscience.co.jp>

  1. … 16 more files in changeset.
Polish support for `@DisplayName` in tests

In particular, remove the need to pass a `hasDisplayNameAnnotation` flag

around, which is too specific for the test descriptors.

  1. … 14 more files in changeset.
Merge branch 'master' of https://github.com/dhirabayashi/gradle into dhirabayashi-master

  1. … 2 more files in changeset.
Add support for serialization of suppressed exceptions

This change serializes the Java 7+ suppressed exceptions similarly

to exception causes. This means that we would try to deserialize

known exceptions and if it's not possible, for example because the

suppressed exception is a custom exception type, then we fallback

on the placeholder exception type.

  1. … 4 more files in changeset.
Add support for serialization of suppressed exceptions

This change serializes the Java 7+ suppressed exceptions similarly

to exception causes. This means that we would try to deserialize

known exceptions and if it's not possible, for example because the

suppressed exception is a custom exception type, then we fallback

on the placeholder exception type.

  1. … 4 more files in changeset.
Add support for serialization of suppressed exceptions

This change serializes the Java 7+ suppressed exceptions similarly

to exception causes. This means that we would try to deserialize

known exceptions and if it's not possible, for example because the

suppressed exception is a custom exception type, then we fallback

on the placeholder exception type.

  1. … 4 more files in changeset.
Try hard to delete files for cleanup

Try hard to delete files for cleanup

Try hard to delete files for cleanup

Try hard to delete files for cleanup

Try hard to delete files for cleanup

Detect special multicause exceptions

This commit fixes an issue where test reports and build scans didn't capture

all the causes of an exception, in case the "multi-cause" exception isn't

a type known of the daemon. By that, we mean a type which is not available

at runtime in the daemon process, but is used in the worker process.

Typically, the `org.opentest4j.MultipleFailuresError` type used by

JUnit is such an example: the type is used in a test process, but

not loaded in Gradle. In such cases, Gradle builds a placeholder

exception type which collects the root cause. But in case the

exception is actually collecting multiple causes like in this test

class, Gradle lost some information in the process.

Therefore, this commit introduces a heuristic to figure out if an

exception is collecting multiple causes instead of a single one.

The heuristic is kept very simple: one has to find a method which

name is either `getCauses` (like for Gradle's own default multi

cause exception) or `getFailures` (like in opentest4j), and it

has to return a collection of failures.

This will not fix all problems but it should capture a good amount

of them.

Fixes #9487

  1. … 3 more files in changeset.
Detect special multicause exceptions

This commit fixes an issue where test reports and build scans didn't capture

all the causes of an exception, in case the "multi-cause" exception isn't

a type known of the daemon. By that, we mean a type which is not available

at runtime in the daemon process, but is used in the worker process.

Typically, the `org.opentest4j.MultipleFailuresError` type used by

JUnit is such an example: the type is used in a test process, but

not loaded in Gradle. In such cases, Gradle builds a placeholder

exception type which collects the root cause. But in case the

exception is actually collecting multiple causes like in this test

class, Gradle lost some information in the process.

Therefore, this commit introduces a heuristic to figure out if an

exception is collecting multiple causes instead of a single one.

The heuristic is kept very simple: one has to find a method which

name is either `getCauses` (like for Gradle's own default multi

cause exception) or `getFailures` (like in opentest4j), and it

has to return a collection of failures.

This will not fix all problems but it should capture a good amount

of them.

Fixes #9487

  1. … 3 more files in changeset.
Merge branch 'master' into master

  1. … 8 more files in changeset.
If @DisplayName annotation is attached, output the annotation value to name attribute of testsuite and name attribute of testcase. If @DisplayName annotation is not attached, output the class FQN. In any case, output the class FQN to classname attribute of testcase.

Issue: #11445

Signed-off-by: Daiki Hirabayashi <hirabayashi@infoscience.co.jp>

  1. … 21 more files in changeset.
Fix for changes to parallelism configuration.

Replace `ParallelismConfigurationListener` and `ParallelismConfigurationManager` and some mutable state with a service of type `ParallelismConfiguration`.

  1. … 31 more files in changeset.
Replace `ParallelismConfigurationListener` and `ParallelismConfigurationManager` and some mutable state with a service of type `ParallelismConfiguration`.

  1. … 31 more files in changeset.
Replace `ParallelismConfigurationListener` and `ParallelismConfigurationManager` and some mutable state with a service of type `ParallelismConfiguration`.

  1. … 31 more files in changeset.
Replace `ParallelismConfigurationListener` and `ParallelismConfigurationManager` and some mutable state with a service of type `ParallelismConfiguration`.

  1. … 31 more files in changeset.
Replace `ParallelismConfigurationListener` and `ParallelismConfigurationManager` and some mutable state with a service of type `ParallelismConfiguration`.

  1. … 30 more files in changeset.
Replace `ParallelismConfigurationListener` and `ParallelismConfigurationManager` and some mutable state with a service of type `ParallelismConfiguration`.

  1. … 30 more files in changeset.
Replace `ParallelismConfigurationListener` and `ParallelismConfigurationManager` and some mutable state with a service of type `ParallelismConfiguration`.

  1. … 30 more files in changeset.