StaleOutputIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Annotate tests for instant execution after recent changes

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

  1. … 16 more files in changeset.
Annotate tests for instant execution after recent changes

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

  1. … 20 more files in changeset.
Annotate tests for instant execution after recent changes

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

  1. … 20 more files in changeset.
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

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

  1. … 872 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after first round of CI feedback

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

  1. … 58 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after first round of CI feedback

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

  1. … 58 more files in changeset.
Add test for #8299 (#8313)

Seems like #8299 has been fixed between 5.1.1 and the current release branch. I am adding this test so it won't come back.

    • -0
    • +33
    ./StaleOutputIntegrationTest.groovy
Remove history after no-source outputs have been cleaned (#8036)

So it is as if the task never executed.

  1. … 7 more files in changeset.
Fix problems with file tree outputs

    • -0
    • +44
    ./StaleOutputIntegrationTest.groovy
  1. … 1 more file in changeset.
Fix non-detected stale output file removal (#4264)

    • -6
    • +71
    ./StaleOutputIntegrationTest.groovy
  1. … 20 more files in changeset.
Add failing test for cleanup of stale local state

    • -0
    • +80
    ./StaleOutputIntegrationTest.groovy
Remove leftover debug switch

Fix tests

  1. … 4 more files in changeset.
Resolve singular output properties properly

  1. … 1 more file in changeset.
Create directories when registering outputs via the runtime API, too (#2929)

Previously we were creating output directories only for outputs registered via task property annotations.

  1. … 32 more files in changeset.
Cleanup directories when sources become empty (#2611)

Cleanup directories when sources become empty and not only files.

- Improved performance for SkipEmptySourceFilesTaskExecuter

It is not necessary to resolve a FileCollection when checking if the

previous execution had output files.

Moreover, we now record the empty output files after we deleted them,

so the task has to do less work next time.

    • -3
    • +13
    ./StaleOutputIntegrationTest.groovy
  1. … 13 more files in changeset.
Show cleanup message only when files are deleted

+review REVIEW-6557

    • -0
    • +14
    ./StaleOutputIntegrationTest.groovy
  1. … 1 more file in changeset.
Cleanup stale output files during execution (#2572)

We now keep a registry of all the outputs generated by Gradle which will be reset on each version change. If Gradle encounters an existing output file, then it will remove it if is not part of the registered outputs and owned by Gradle/the build. We do also not remove directories containing outputs from different tasks.

The check to delete the stale outputs happens now just before the task executes and not up-front as it did before.

The `build` directory and all delete targets of the `clean` task are registered as owned by Gradle and are considered safe to delete.

Currently, the set of recorded task output files is only growing if we do not change the Gradle version. In the future we can improve on this by also detecting that some directories where removed (e.g. by running a clean task) and reflect this in the registry.

Fixes #1168

Fixes #973

+review REVIEW-6557

    • -73
    • +398
    ./StaleOutputIntegrationTest.groovy
  1. … 32 more files in changeset.
Use separate output directories for all JVM languages

- Introduce an outputDir on SourceDirectorySet

- Default output directory is now `build/classes/<source directory set name>/<source set name>`

- Example: Java compilation goes to build/classes/java/main instead of build/classes/main

- Adapt JDepend, FindBugs, Test and ValidateTaskProperties tasks to handle multiple class directories

- Deprecate setClassesDir/getClassesDir on SourceSetOutput

- Calling setClassesDir restores old behavior (shared output directory)

- Introduce addClassesDir and getClassesDirs on SourceSetOutput

- OSGi plugin needs a single classes directory, so introduce 'osgiClasses' task that syncs all classes to a single directory

Most of the changes to integration tests are find classes in their new location. Helper methods in AbstractIntegrationSpec

can locate class files vs hardcoding a path.

Squashed commit of sg-split-jvm-classes branch for REVIEW-6502

  1. … 119 more files in changeset.
Fix integration tests

+review REVIEW-6424

    • -44
    • +16
    ./StaleOutputIntegrationTest.groovy
  1. … 1 more file in changeset.
Add checks for custom target files and flip-flop gradle versions

+review REVIEW-6424

    • -0
    • +62
    ./StaleOutputIntegrationTest.groovy
Spec and test cases for removing JavaCompile stale output (#984)

Spec and test cases for removing JavaCompile stale output

    • -27
    • +0
    ./StaleOutputIntegrationTest.groovy
  1. … 2 more files in changeset.
Use JarTestFixture to prevent file leaking on Windows

+review REVIEW-6352

Add test demonstrating GRADLE-1501

+review REVIEW-6352

    • -0
    • +28
    ./StaleOutputIntegrationTest.groovy
Removed unnecessary comments

We usually don't use these as they are hard to keep in sync with the actual code changes.

+review REVIEW-6267

    • -15
    • +15
    ./StaleOutputIntegrationTest.groovy
GRADLE-2579 - Getting rid of stale output files.

    • -0
    • +112
    ./StaleOutputIntegrationTest.groovy
  1. … 8 more files in changeset.