HttpTaskOutputCacheJavaPerformanceTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Consolidate build cache performance tests

There is now only one class which contains all the tests. We now always

have the local cache enabled (push = true), since this is the default

use case. For the remote cache tests we clean the local cache after each

run.

We also added a new test which tests pushing to the remote build cache.

+review REVIEW-6556

    • -136
    • +0
    ./HttpTaskOutputCacheJavaPerformanceTest.groovy
  1. … 2 more files in changeset.
Rename test HTTP build cache server to HttpBuildCacheServer

+review REVIEW-6548

    • -11
    • +11
    ./HttpTaskOutputCacheJavaPerformanceTest.groovy
  1. … 7 more files in changeset.
Address review items

+review REVIEW-6503

    • -1
    • +2
    ./HttpTaskOutputCacheJavaPerformanceTest.groovy
  1. … 6 more files in changeset.
Remove deprecated task caching system properties

+review REVIEW-6503

    • -20
    • +10
    ./HttpTaskOutputCacheJavaPerformanceTest.groovy
  1. … 13 more files in changeset.
Add authentication support to HttpServerFixture

This allows to enable authentication on the BuildCache for

integration tests.

+review REVIEW-6479

    • -0
    • +1
    ./HttpTaskOutputCacheJavaPerformanceTest.groovy
  1. … 14 more files in changeset.
Streamline naming of performance tests: build cache tests

    • -7
    • +5
    ./HttpTaskOutputCacheJavaPerformanceTest.groovy
  1. … 2 more files in changeset.
Improve check to not match version 3.4.1

    • -1
    • +1
    ./HttpTaskOutputCacheJavaPerformanceTest.groovy
Cleanup Java performance test projects and scenarios

- Sort tests into packages

- Add new test projects: `largeMonolithicJavaProject`,

`largeJavaMultiProject`, `mediumJavaMultiProjectWithTestNG`

- Cleanup template.gradle file

-- Remove "old Java" templates

-- Remove unused Scala and Groovy performance

test project configurations

-- Remove large enterprise performance test projects

- Simplify Java scenarios: clean assemble, first use, change test,

getting IDE models, dependency report, abi change, non-abi change

- Adjust tests to not use old test projects anymore

- Add file mutators

    • -0
    • +146
    ./HttpTaskOutputCacheJavaPerformanceTest.groovy
  1. … 96 more files in changeset.
Redirect output of performance tests to disk

The performance tests now no longer use our integration test fixtures.

Instead they use a simple ProcessBuilder to be closer to what a user

would do. More specifically, we no longer capture output in the test VM,

as that can introduce its own flakiness into the measurement. It also

reduces the memory needed to run the performance tests. Last but not least

spooling the output to disk makes later analysis easier.

    • -2
    • +2
    ./HttpTaskOutputCacheJavaPerformanceTest.groovy
  1. … 9 more files in changeset.
Initial version of simplified test project generator

Dependencies between sources and projects are still missing.

    • -1
    • +1
    ./HttpTaskOutputCacheJavaPerformanceTest.groovy
  1. … 21 more files in changeset.