IvySftpRepoErrorsIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove unnecessary `skip = FAILS_CLEANUP_ASSERTIONS` from tests

    • -7
    • +7
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 35 more files in changeset.
Add `FAILS_CLEANUP_ASSERTIONS` to `IvySftpRepoErrorsIntegrationTest`

    • -17
    • +17
    ./IvySftpRepoErrorsIntegrationTest.groovy
Annotate tests to account for new reported problems

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

    • -1
    • +9
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 48 more files in changeset.
Annotate tests to account for new reported problems

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

    • -1
    • +9
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 48 more files in changeset.
Annotate tests that now properly report problems

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

    • -1
    • +9
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 21 more files in changeset.
Annotate tests to account for new reported problems

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

    • -1
    • +9
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 49 more files in changeset.
Annotate tests to account for new reported problems

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

    • -1
    • +9
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 49 more files in changeset.
Annotate tests to account for new reported problems

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

    • -1
    • +9
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 49 more files in changeset.
Annotate tests that now properly report problems

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

    • -1
    • +9
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 21 more files in changeset.
Fixes for previous commits.

    • -8
    • +1
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 5 more files in changeset.
Do not write the source paths for a `CopySpec` multiple times to the instant execution cache.

Previously, these were written once when the `CopySpec` was serialized and once when the associated input property spec was serialized.

This commit adds some special case handling for this case. It also preserves the identity of each `FileTree` and `FileCollection` instance for each task to enable short circuiting when the same file collections are referenced via multiple paths, such as in the `CopySpec` case.

    • -8
    • +1
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 42 more files in changeset.
Do not write the source paths for a `CopySpec` multiple times to the instant execution cache.

Previously, these were written once when the `CopySpec` was serialized and once when the associated input property spec was serialized.

This commit adds some special case handling for this case. It also preserves the identity of each `FileTree` and `FileCollection` instance for each task to enable short circuiting when the same file collections are referenced via multiple paths, such as in the `CopySpec` case.

    • -8
    • +1
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 42 more files in changeset.
Do not write the source paths for a `CopySpec` multiple times to the instant execution cache.

Previously, these were written once when the `CopySpec` was serialized and once when the associated input property spec was serialized.

This commit adds some special case handling for this case. It also preserves the identity of each `FileTree` and `FileCollection` instance for each task to enable short circuiting when the same file collections are referenced via multiple paths, such as in the `CopySpec` case.

    • -8
    • +1
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 42 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>

    • -7
    • +7
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 18 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>

    • -7
    • +7
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 18 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>

    • -7
    • +7
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 18 more files in changeset.
Rename @ToBeFixedForInstantExecution.value to skip for explicitness

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

    • -7
    • +7
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 36 more files in changeset.
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

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

    • -8
    • +8
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 872 more files in changeset.
Move skip reasons to @FailsWithInstantExecution and drop @IgnoreWithInstantExecution

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

    • -8
    • +8
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 45 more files in changeset.
Annotate integ tests failing to cleanup with instant execution in :resourcesSftp

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

    • -8
    • +8
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 7 more files in changeset.
Annotate integ tests failing with instant execution in :resourcesSftp

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

    • -0
    • +8
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 4 more files in changeset.
Annotate integ tests failing with instant execution in :resourcesSftp

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

    • -0
    • +8
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 4 more files in changeset.
Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

    • -0
    • +1
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 12 more files in changeset.
Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

    • -0
    • +1
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 12 more files in changeset.
Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

    • -0
    • +1
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 12 more files in changeset.
Merge resources integration tests

    • -253
    • +0
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 123 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -2
    • +0
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 95 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -2
    • +0
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 15 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -2
    • +0
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 15 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -2
    • +0
    ./IvySftpRepoErrorsIntegrationTest.groovy
  1. … 15 more files in changeset.