Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Force AbstractTestDirectoryProvider to use Class (#12431)

Closes https://github.com/gradle/gradle-private/issues/2988

This PR adds `className` to `AbstractTestDirectoryProvider` so there'll be no more `unknown-test-class`.

  1. … 407 more files in changeset.
Fix tests

  1. … 372 more files in changeset.
Fix module metadata for Maven snapshot

In the context of Maven snapshots, the name of the artifact is the GAV

without replacing the -SNAPSHOT, while the file is indeed the unique

timestamped version.

  1. … 11 more files in changeset.
Re-annotate some tests still leaking file handles

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

Re-annotate some tests still leaking file handles

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

  1. … 4 more files in changeset.
Re-annotate some tests still leaking file handles

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

  1. … 5 more files in changeset.
Re-annotate some tests still leaking file handles

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

  1. … 5 more files in changeset.
De-skip tests that don't leak files anymore

but still fail with instant execution

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

  1. … 16 more files in changeset.
De-skip tests that don't leak files anymore

but still fail with instant execution

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

  1. … 16 more files in changeset.
De-skip tests that don't leak files anymore

but still fail with instant execution

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

  1. … 16 more files in changeset.
Rename @ToBeFixedForInstantExecution.value to skip for explicitness

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

  1. … 34 more files in changeset.
Fix direct get resource for GCS (#11669)

It looks like this code path was never properly tested and working

since this was implemented. It was only working for the case

where we have a populated cache (Maven local) and probe for

metadata before downloading.

Fix direct get resource for GCS

It looks like this code path was never properly tested and working

since this was implemented. It was only working for the case

where we have a populated cache (Maven local) and probe for

metadata before downloading.

Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

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

  1. … 867 more files in changeset.
Move skip reasons to @FailsWithInstantExecution and drop @IgnoreWithInstantExecution

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

  1. … 43 more files in changeset.
Annotate integ tests failing to cleanup with instant execution in :resourcesGcs

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

Annotate integ tests failing with instant execution in various projects

removing most of @IgnoreWithInstantExecution annotations

after fixing the @FailsWithInstantExecution rule

and more ci feedback

also make @IgnoreWithInstantExecution require a reason from a fixed set

and add it to the remaining ignores

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

  1. … 124 more files in changeset.
Annotate integ tests failing with instant execution in :resourcesGcs

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

Annotate integ tests failing with instant execution in :resourcesGcs

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

Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

  1. … 9 more files in changeset.
Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

  1. … 9 more files in changeset.
Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

  1. … 9 more files in changeset.
Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

  1. … 9 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

  1. … 32 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

  1. … 32 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

  1. … 32 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

  1. … 32 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

  1. … 32 more files in changeset.
Make http server fixture's handle() thread safe

As stated in the here implemented 'ServerWithExpectations' fixture:

"handlers, as well as failures, need to be thread-safe"

This concrete case was working most of the time since usually there are

not more than one expectations for the same request. But if the

same request is expected several times, and the requests are received

in parallel (as it is the case for metadata download), the handle()

method behaved flaky - by not doing reading and updating of the 'run'

flag as an atomic operation.

  1. … 4 more files in changeset.
Make http server fixture's handle() thread safe

As stated in the here implemented 'ServerWithExpectations' fixture:

"handlers, as well as failures, need to be thread-safe"

This concrete case was working most of the time since usually there are

not more than one expectations for the same request. But if the

same request is expected several times, and the requests are received

in parallel (as it is the case for metadata download), the handle()

method behaved flaky - by not doing reading and updating of the 'run'

flag as an atomic operation.

  1. … 4 more files in changeset.