ToolingApiLoggingCrossVersionSpec.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Split TAPI tests to dedicated source sets

    • -152
    • +0
    ./ToolingApiLoggingCrossVersionSpec.groovy
  1. … 346 more files in changeset.
Fix flakiness introduced by switching test to run with daemon #2

    • -2
    • +5
    ./ToolingApiLoggingCrossVersionSpec.groovy
Fix flakiness introduced by switching test to run with daemon

    • -5
    • +9
    ./ToolingApiLoggingCrossVersionSpec.groovy
Adjust test for parallel execution

    • -1
    • +1
    ./ToolingApiLoggingCrossVersionSpec.groovy
Adjust test to daemon-by-default behavior

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

    • -1
    • +4
    ./ToolingApiLoggingCrossVersionSpec.groovy
  1. … 37 more files in changeset.
Also log all output to standard streams in TAPI logging test

This can give additional hints to why the test is occasionally failing.

    • -3
    • +12
    ./ToolingApiLoggingCrossVersionSpec.groovy
Wire integration test build context instance

- enables using performance test specific build context when an instance

is properly wired

    • -1
    • +1
    ./ToolingApiLoggingCrossVersionSpec.groovy
  1. … 48 more files in changeset.
Restrict cross-version test to TAPI >= 2.2

In order to use an isolated TAPI client in this test, we need to

instantiate a `DefaultGradleConnection` directly from the service

registry. This doesn't work for TAPI v2.0 and v2.1.

    • -0
    • +2
    ./ToolingApiLoggingCrossVersionSpec.groovy
Use an isolated tooling client for integrations to close

Some tests require that the tooling client be closed or reset, either

to verify the behaviour on close or to ensure that certain sticky state

is reset. Previously, these tests were interfering with other,

unrelated tests.

These tests now use an isolated tooling client, so that they don't

impact the static state of the shared tooling client used by the rest

of the integration tests.

Flaky test: gradle/gradle-private#480

    • -10
    • +2
    ./ToolingApiLoggingCrossVersionSpec.groovy
  1. … 4 more files in changeset.
Temporarily ignore some TAPI tests that might be causing flakiness

These 2 cross-version tests use static methods to shut down the TAPI

client connection. I suspect that this might be causing shutdown

requests to be sent in other unrelated tests. These shutdown requests

are harmless in many cases, but they cause issues in tests for

cancellation of continuous build.

    • -0
    • +3
    ./ToolingApiLoggingCrossVersionSpec.groovy
  1. … 1 more file in changeset.
Temporarily ignore some TAPI tests that might be causing flakiness

These 2 cross-version tests use static methods to shut down the TAPI

client connection. I suspect that this might be causing shutdown

requests to be sent in other unrelated tests. These shutdown requests

are harmless in many cases, but they cause issues in tests for

cancellation of continuous build.

    • -0
    • +3
    ./ToolingApiLoggingCrossVersionSpec.groovy
  1. … 1 more file in changeset.
Indicate that test running with isolated home dir may leak file handle

    • -0
    • +4
    ./ToolingApiLoggingCrossVersionSpec.groovy
Make tests that close the TAPI (via reset()) require an isolated daemon

+review REVIEW-6310

    • -0
    • +1
    ./ToolingApiLoggingCrossVersionSpec.groovy
  1. … 1 more file in changeset.
Removed some test fixture logic that is no longer required given the new minimum versions supported by the tooling API.

    • -3
    • +0
    ./ToolingApiLoggingCrossVersionSpec.groovy
  1. … 1 more file in changeset.
Renamed `GradleExecuter.requireGradleHome` -> `requireGradleDistribution`

    • -1
    • +1
    ./ToolingApiLoggingCrossVersionSpec.groovy
  1. … 29 more files in changeset.
Fixed test expectations.

    • -1
    • +1
    ./ToolingApiLoggingCrossVersionSpec.groovy
Generate a warning when Gradle is invoked from tooling api clients older than 2.0. This will be turned into an error in Gradle 3.0.

    • -0
    • +2
    ./ToolingApiLoggingCrossVersionSpec.groovy
  1. … 2 more files in changeset.
Issue a deprecation warning when using the tooling API to run a build using Gradle 1.1 or older. This will be changed to an error in Gradle 3.0.

    • -0
    • +1
    ./ToolingApiLoggingCrossVersionSpec.groovy
  1. … 6 more files in changeset.
Changed test to disable deprecation message stack traces when generating output to use to compare against that produced from the tooling api.

    • -0
    • +1
    ./ToolingApiLoggingCrossVersionSpec.groovy
Fixed some more tests that were broken on machines where the line separator is not '\n'.

    • -2
    • +2
    ./ToolingApiLoggingCrossVersionSpec.groovy
  1. … 3 more files in changeset.
Workaround for test failure. Still needs a real fix.

    • -0
    • +1
    ./ToolingApiLoggingCrossVersionSpec.groovy
Changed a bunch of tooling api logging tests so that they don't force daemon mode, now that logging mostly works in embedded mode. Removed some duplicate test coverage.

    • -4
    • +2
    ./ToolingApiLoggingCrossVersionSpec.groovy
  1. … 7 more files in changeset.
Removed sys property that is not required for this test

    • -1
    • +0
    ./ToolingApiLoggingCrossVersionSpec.groovy
minor formatting.

    • -4
    • +4
    ./ToolingApiLoggingCrossVersionSpec.groovy
Run with `--no-daemon` in order to suppress any warnings about lack of daemon use.

    • -5
    • +1
    ./ToolingApiLoggingCrossVersionSpec.groovy
Make sure that daemon starting message does not interfere ToolingApiLoggingCrossVersionSpec when running using daemon executer.

+review REVIEW-5426

    • -0
    • +1
    ./ToolingApiLoggingCrossVersionSpec.groovy
Codenar

+review REVIEW-5426

    • -1
    • +0
    ./ToolingApiLoggingCrossVersionSpec.groovy
Suppress daemon suggestion usage message when simulating command line execution for logging comparison with tooling api.

+review REVIEW-5426

    • -1
    • +13
    ./ToolingApiLoggingCrossVersionSpec.groovy
Removed filtering for message that is no longer generated.

    • -6
    • +1
    ./ToolingApiLoggingCrossVersionSpec.groovy