GradleRunnerBuildFailureIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Disable IntegrationTestFixtures rule on test kit

as it uses different test fixtures.

    • -0
    • +1
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 2 more files in changeset.
Clean up test fixtures, add more context to error messages, add some test coverage.

    • -55
    • +17
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 8 more files in changeset.
Fix various cross version tests for changes to log output.

    • -2
    • +32
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 8 more files in changeset.
Move warning summary to immediately before build summary

This makes it much more likely that the last 2 things the user will

see in order are: warning summary then build summary (then

build scan link, if configured)

Issue: #4042

Signed-off-by: Eric Wendelin <eric@gradle.com>

    • -1
    • +1
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 11 more files in changeset.
Fix more tests

    • -2
    • +1
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 4 more files in changeset.
Fix some tests that check output

    • -2
    • +4
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 8 more files in changeset.
Use common output chain for grouping and header generation

This allows us to group logs for print streams like stdout and stderr.

Use PrettyPrefix header for all output chains, making our output

consistent between rich and plain console modes.

Adjust functional test coverage to accomodate for new task header

    • -15
    • +13
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 111 more files in changeset.
Fix some integration tests

    • -13
    • +13
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 2 more files in changeset.
Fix integ test expectations (2d try)

    • -6
    • +1
    ./GradleRunnerBuildFailureIntegrationTest.groovy
Fix integration tests expectations

    • -0
    • +2
    ./GradleRunnerBuildFailureIntegrationTest.groovy
Group logs in all environments

Allow renderer to specify header formatter and whether all

log headers should be rendered and use that for standard streams

output (e.g. plain console, piped output, etc.)

Set build operation display status for completed tasks

Build Operations can set a status through the build operation

context. Status is forwarded on through the build operation

executor upon completion.

Replace TaskExecutionLogger with progress logs generated from

build operation events through the task graph executer.

Issue: #1985

    • -13
    • +10
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 26 more files in changeset.
Change default log level to WARN (#1952)

    • -5
    • +7
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 44 more files in changeset.
Report task outcome statistics after build finishes

This changes the format of the Build Result to have consistent

duration display to the console.

- Move TerseDurationFormatter and reuse it for BuildResultLogger.

Inject a DurationFormatter into the BuildResultLogger with a

concrete TersePrettyDurationFormatter impl.

- Remove cache stats reporting

- Fix tests that scrape build result message

Issue: #1639

    • -12
    • +6
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 37 more files in changeset.
Changed test kit int tests to normalize build output in the same way that build test fixtures do.

    • -19
    • +23
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 1 more file in changeset.
Simplify and remove artificial constraints on GradleRunner tests.

+review

    • -80
    • +77
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 46 more files in changeset.
Simplify and unify how the Gradle version to use is selected based on the test's charecteristics.

+review REVIEW-5698

    • -10
    • +6
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 17 more files in changeset.
Make the test kit runner an inner class of the base class, as they are closely related.

+review REVIEW-5698

    • -1
    • +1
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 15 more files in changeset.
Introduce and use annotation for capturing executed tasks

+review REVIEW-5698

    • -0
    • +2
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 9 more files in changeset.
Fail the build if build result output is accessed with Gradle < 2.9 in debug mode

+review REVIEW-5698

    • -0
    • +3
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 19 more files in changeset.
Moved annotations to subpackage

+review REVIEW-5698

    • -1
    • +1
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 19 more files in changeset.
Enable compatibility testing for integration tests

Execute all tests against with multiple Gradle versions. This is meant as a first run of the tests to see how much it add to the overal build execution time. It's likely that we need a dedicated CI job.

+review REVIEW-5698

    • -1
    • +3
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 8 more files in changeset.
Improvements to the handling of build output with GradleRunner.

- Don't separate stdout and stderr for the output component of the build result

- Have forwardOutput() forward stdout and stderr to the System.out of the client (opposed to splitting)

- Rename to forwardStdOut() and forwardStdErr()

- Don't treat Tooling API connection failures as failed builds

- De-tangle the IO object pieces so that they make sense in isolation

- When forwarding from the build to the clients stdout, don't encode just to decode again (i.e. passthru)

- Polish on the Javadoc and release notes for this feature

+review REVIEW-5654

    • -21
    • +14
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 29 more files in changeset.
Don't duplicate the underlying exception for an unexpected build result in the message of the unexpected build result exception.

+review REVIEW-5654

    • -6
    • +1
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 3 more files in changeset.
Expose BuildResult for UnexpectedBuildFailure and UnexpectedBuildSuccess.

+review REVIEW-5636

    • -3
    • +20
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 4 more files in changeset.
Change the `TaskResult` enum to `TaskOutcome`.

After working with this a little, the overloaded uses of `result` became slightly problematic. Moreover, “outcome” is slightly more accurate as if you squint and look sideways it has a more constrained scope than the term “result”.

+review REVIEW-5533

    • -1
    • +1
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 17 more files in changeset.
Some tweaks to requirement of a project directory with the test kit.

+review REVIEW-5533

    • -2
    • +2
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 3 more files in changeset.
Cover the case where a user provides a task that is not defined by the executed build script.

+review REVIEW-5533

    • -0
    • +19
    ./GradleRunnerBuildFailureIntegrationTest.groovy
Ensure that a project directory is assigned before executing the build.

+review REVIEW-5533

    • -0
    • +21
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 1 more file in changeset.
Sync some GradleRunner API nomenclature with terms that the Tooling API uses, for no other reason than an attempt at consistency.

+review REVIEW-5533

    • -6
    • +6
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 11 more files in changeset.
More polishing and documenting of GradleRunner API.

+review REVIEW-5533

    • -4
    • +4
    ./GradleRunnerBuildFailureIntegrationTest.groovy
  1. … 12 more files in changeset.