JavaFirstUsePerformanceTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rebaseline JavaFirstUsePerformanceTest

See https://github.com/gradle/gradle-private/issues/2797

Rebaseline to unblock pipeline after dependency upgrade

After upgrading dependencies, there's a huge regression in runtime jar shading

process. This commit rebaselines affected performance tests.

See more details in https://github.com/gradle/gradle-private/issues/2767

Rebaseline to unblock pipeline after dependency upgrade

After upgrading dependencies, there's a huge regression in runtime jar shading

process. This commit rebaselines affected performance tests.

See more details in https://github.com/gradle/gradle-private/issues/2767

Create a new category for slow performance regression tests

  1. … 8 more files in changeset.
Accept a tiny performance regression

Rebaseline to accept a tiny regression

Rebase to latest 6.0 nightly

#10348 has an influence on some of these performance scenarios.

(correcting 90e852d and 85933bb)

  1. … 29 more files in changeset.
Rebase performance tests with 5.7-20190722220035+0000 baseline

#10348 might have an influence on the performance of these scenarios.

  1. … 25 more files in changeset.
Remove GFileUtils.cleanDirectory()

  1. … 6 more files in changeset.
Convert JavaFirstUsePerformanceTest to use Gradle profiler

    • -21
    • +15
    ./JavaFirstUsePerformanceTest.groovy
  1. … 1 more file in changeset.
Convert JavaFirstUsePerformanceTest to use Gradle profiler

    • -19
    • +13
    ./JavaFirstUsePerformanceTest.groovy
  1. … 1 more file in changeset.
Convert JavaFirstUsePerformanceTest to use Gradle profiler

    • -21
    • +15
    ./JavaFirstUsePerformanceTest.groovy
  1. … 1 more file in changeset.
Convert JavaFirstUsePerformanceTest to use Gradle profiler

    • -21
    • +23
    ./JavaFirstUsePerformanceTest.groovy
  1. … 1 more file in changeset.
Rename performance test infrastructure legacy classes

To make clear that they are using the Gradle build internal

infrastructure.

  1. … 44 more files in changeset.
Rebaseline all performance test scenarios

There seems to be tiny gradual regression in performance, which causes unbearable

flakiness. Rebaselining all scenarios to catch future regressions.

  1. … 30 more files in changeset.
Rebaseline to latest nightly

Looking at the history, last rebaselining seems not to use the right version,

so this is rebaselining to latest nightly.

  1. … 1 more file in changeset.
Rebaseline to latest nightly

Looking at the history, last rebaselining seems not to use the right version,

so this is rebaselining to latest nightly.

  1. … 1 more file in changeset.
Try latest nightly

  1. … 35 more files in changeset.
Try latest nightly

  1. … 35 more files in changeset.
Rebase `clean checkout` performance tests

There is a small regression in it. The regression seems to be the same

as we have for the `buildSrc` change tests, which we already accepted.

Rebase first use performance tests

Rework rebaseline JavaFirstUsePerformanceTest

This is a rework of 8b78c1339e6f444e0404c1b58894c01ed5f4354e with 5.6 nightly.

Rebaseline clean checkout scenarios

Accept the regression of improving task constrctor caching.

https://github.com/gradle/gradle/pull/9682

Revert "Rebaseline 'first use of largeJavaMultiProject' temporarily"

This reverts commit 6d77bce974013e34e4a84248aae956885500d7fb.

Rebaseline 'first use of largeJavaMultiProject' temporarily

Rebaseline JavaFirstUsePerformanceTest

Lock-in some performance improvements

  1. … 31 more files in changeset.
Rebaseline first use and clean checkout perf tests

While the investigation is ongoing, so no new regressions are

introduced.

See https://github.com/gradle/gradle-private/issues/2213

Rebaseline flaky performance tests to latest nightly

  1. … 1 more file in changeset.
Rebaseline improved scenarios