StaleOutputHistoryLossIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

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

    • -5
    • +5
    ./StaleOutputHistoryLossIntegrationTest.groovy
  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>

    • -0
    • +5
    ./StaleOutputHistoryLossIntegrationTest.groovy
  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>

    • -0
    • +5
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 58 more files in changeset.
Make paths/names of included builds immutable (#10998)

Changes the “build path” for included builds to be determined at inclusion time based on the directory name, or a user supplied override. Previously, we tried to use the root project name defined in the included build. This caused a lot of complexity due to it not being known until part way through building the included build.

This change also disallows use of `buildSrc` as a project name, as it collides with the `buildSrc` nested build.

    • -40
    • +0
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 72 more files in changeset.
Disallow builds defining a project at :buildSrc

This is already prohibited by the composite build machinery if there is

also a real buildSrc project. This change makes the failure earlier and

more obvious.

    • -40
    • +0
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 8 more files in changeset.
Merge remote-tracking branch 'origin/sg/60/jdk13'

* origin/sg/60/jdk13:

Tweak comment about support for JDK12

Remove VERSION_14 for now

Refactor test dependency declarations for archunit

Add release notes and features for JDK13 support

Use new version for Scala 2.12 in Play

Bump versions in build-init

Make codenarc happy

Handle 'Connection reset' as end-of-stream failures too

Avoid JDK13 aggressive whitespace trimming when using stripIndent

Update archunit to a version that supports JDK13

Ignore older versions of Gradle if they do not support the current JVM

Fix more stripIndent usages for JDK13

Support more possible JDK13 error messages

Adjust expected error message for JDK13

Adjust multi-line strings to work with both Groovy and JDK13 stripIndent methods

Add VERSION_13 and VERSION_14 to JavaVersion

Restrict support for JDK13 to versions after 5.6

    • -0
    • +4
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 2 more files in changeset.
Clean up upgrading doc and reintroduce test

    • -0
    • +41
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 1 more file in changeset.
Remove references to task removal

    • -46
    • +0
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 2 more files in changeset.
Ignore older versions of Gradle if they do not support the current JVM

    • -0
    • +4
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 2 more files in changeset.
Ignore older versions of Gradle if they do not support the current JVM

    • -0
    • +4
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 2 more files in changeset.
Ignore older versions of Gradle if they do not support the current JVM

    • -0
    • +4
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 2 more files in changeset.
Increase timeout for StaleOutputHistoryLossIntegrationTest

This is an attempt of fixing https://github.com/gradle/gradle-private/issues/1605

    • -1
    • +1
    ./StaleOutputHistoryLossIntegrationTest.groovy
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -5
    • +5
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 50 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -5
    • +5
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 98 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -5
    • +5
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 98 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -5
    • +5
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 50 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -5
    • +5
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 98 more files in changeset.
Expect deprecation warning on more tests regarding task removal

    • -0
    • +1
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 1 more file in changeset.
Set timeout for AbstractIntegrationSpec (#5806)

We have been bitten by CI build exection timeout for a long time.

This PR introduces timeout for AbstractIntegrationSpec in order to

monitor execution timeout. Upon timeout, a spock interceptor can

print all threads' stack traces in all JVMs so that we can diagnose

the potential issues in other JVMs (daemons, test workers, etc.).

    • -2
    • +2
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 29 more files in changeset.
Fix integ test usages of output test fixtures

    • -4
    • +6
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 6 more files in changeset.
Rename methods on `ReleasedVersionDistributions`

So they match more closely what they really return.

    • -4
    • +4
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 9 more files in changeset.
Fix integration test

Now that 4.2 is out we can use this version in the test. No need to use

a snapshot any more.

    • -5
    • +1
    ./StaleOutputHistoryLossIntegrationTest.groovy
Fix integration test

Now that 4.2 is out we can use this version in the test. No need to use

a snapshot any more.

    • -5
    • +1
    ./StaleOutputHistoryLossIntegrationTest.groovy
Consider source set outputs as safe to delete

+review REVIEW-6557

    • -12
    • +48
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 2 more files 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

    • -49
    • +20
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 32 more files in changeset.
Show stale output cleanup message on info level

    • -0
    • +6
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 4 more files in changeset.
Set default log level back to LIFECYCLE (#2015)

    • -7
    • +0
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 41 more files in changeset.
Move "Deleted" message to info and stale outputs to incremental section

+review REVIEW-6521

    • -2
    • +2
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 3 more files in changeset.
Use a nightly snapshot vs previous release for stale output detection tests

+review REVIEW-6502

    • -3
    • +2
    ./StaleOutputHistoryLossIntegrationTest.groovy
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

    • -0
    • +2
    ./StaleOutputHistoryLossIntegrationTest.groovy
  1. … 119 more files in changeset.