ContinuousBuildChangeReportingIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Enable tests which should be fixed now

    • -2
    • +0
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 4 more files in changeset.
Enable tests which should be fixed now

    • -2
    • +0
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 4 more files in changeset.
Enable tests which should be fixed now

    • -2
    • +0
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 4 more files in changeset.
Change `value` to `because` in @ToBeFixedForVfsRetention

    • -1
    • +1
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 13 more files in changeset.
Disable tests which change inputs during the build

#11837

    • -0
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 2 more files in changeset.
Disable tests which change inputs during the build

#11837

    • -0
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 2 more files in changeset.
Disable tests which change inputs during the build

#12163

    • -0
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 2 more files in changeset.
Remove many direct dependencies on 'launcher', as this is an entry point project and so does not (or should not) have any kind of API to compile against.

    • -1
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 30 more files in changeset.
Remove many direct dependencies on 'launcher', as this is an entry point project and so does not (or should not) have any kind of API to compile against.

    • -1
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 31 more files in changeset.
Remove many direct dependencies on 'launcher', as this is an entry point project and so does not (or should not) have any kind of API to compile against.

    • -1
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 31 more files in changeset.
Remove many direct dependencies on 'launcher', as this is an entry point project and so does not (or should not) have any kind of API to compile against.

    • -1
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 31 more files in changeset.
Remove many direct dependencies on 'launcher', as this is an entry point project and so does not (or should not) have any kind of API to compile against.

    • -1
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 31 more files in changeset.
Remove many direct dependencies on 'launcher', as this is an entry point project and so does not (or should not) have any kind of API to compile against.

    • -1
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 30 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after second round of CI feedback

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

    • -2
    • +0
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 32 more files in changeset.
Annotate integ tests failing with instant execution in :launcher

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

    • -0
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 14 more files in changeset.
Annotate integ tests failing with instant execution in :launcher

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

    • -0
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 14 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.

    • -2
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.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.

    • -2
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.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.

    • -2
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.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.

    • -2
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.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.

    • -2
    • +2
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 98 more files in changeset.
Refactor to move the file event watcher to a separate class/factory

    • -1
    • +1
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 10 more files in changeset.
Fixed output when using continuous build and quiet logging together, and added some test coverage for such a thing.

    • -1
    • +15
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 3 more files in changeset.
Ensure that we wait for quiet period in integTest

For continuous build tests that verify detection of changes _during_

build execution, we need to ensure that the build waits long enough

for the changes to be notified. This wait is based on the quiet-period

for file change detection.

Flaky test: gradle/gradle-private#529

    • -8
    • +1
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 2 more files in changeset.
Further attempt to fix flaky test

gradle/gradle-private#447

    • -4
    • +4
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
Use an extended quiet period for test, to avoid race

    • -0
    • +6
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 1 more file in changeset.
Attempt to fix flaky test

If the build doesn't take long enough, it's possible that it will

finish without changed files being detected. This change makes the

build take a little longer on Linux, to avoid this race condition.

    • -8
    • +8
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
Make continuous integration tests work on OSX using sleeps

This is until we have a proper native implementation of the file watcher service

    • -1
    • +9
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 1 more file in changeset.
Add test for change reporting for changes during the build

+review REVIEW-5788

    • -0
    • +24
    ./ContinuousBuildChangeReportingIntegrationTest.groovy
  1. … 1 more file in changeset.
Revise test method names

+review REVIEW-5788

    • -4
    • +4
    ./ContinuousBuildChangeReportingIntegrationTest.groovy