ExcludeRuleMergingPerformanceTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rebaeline all performance tests

Most scenarios haven't been rebaselined since 4 month ago, which makes them

fragile because of the gradual performance regression. Rebaseline all of them.

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 25 more files in changeset.
Rebaseline merge exclude rules

There seems to be small regression for some time now (2%/40ms).

This may be caused by memory pressure.

Rebaselining to unblock master.

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
Refine performance baseline selection logic (#10972)

Refine performance baseline selection logic

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

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 25 more files in changeset.
Refine performance baseline selection logic (#10972)

Refine performance baseline selection logic

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

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 25 more files in changeset.
Refine performance baseline selection logic

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

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 25 more files in changeset.
Rebase to latest 6.0 nightly

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

(correcting 90e852d and 85933bb)

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 29 more files in changeset.
Rebase performance tests with 5.7-20190812122716+0000 baseline

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

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 2 more files in changeset.
Rebase ExcludeRuleMergingPerformanceTest

There seems to be a tiny regression that now pushed this over the

edge sporadically. Possibly related to the rebase in 949aa2c.

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
Merge pull request #10244 from gradle/wolfs/more-profiler-tests

Convert some easy classes to use Gradle profiler

    • -2
    • +2
    ./ExcludeRuleMergingPerformanceTest.groovy
Fix failed historical performance test (#10173)

There're 4 failed historical performance tests.

Two of them are because previously `enableFeaturePreview` was not correctly configured for old Gradle build. This PR fixes them with Gradle version check.

Two of them are because of [this change](https://github.com/gradle/performance-comparisons/commit/c640ae2e31e8c8657e6654791ff02ba26ac95304) using a Gradle 4.6+ API.

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 3 more files in changeset.
Remove newlines added by IDEA

    • -1
    • +0
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 14 more files in changeset.
Convert some easy classes to use Gradle profiler

    • -2
    • +3
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 18 more files in changeset.
Convert some easy classes to use Gradle profiler

    • -2
    • +3
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 19 more files in changeset.
Convert some easy classes to use Gradle profiler

    • -2
    • +3
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 19 more files in changeset.
Convert some easy classes to use Gradle profiler

    • -2
    • +2
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 19 more files in changeset.
Rename performance test infrastructure legacy classes

To make clear that they are using the Gradle build internal

infrastructure.

    • -2
    • +2
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 44 more files in changeset.
Correctly generate settings.gradle with enableFeaturePreview

Previously enableFeaturePreview was ignored for single project build.

This commit fixes them with Gradle version check.

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 1 more file in changeset.
Correctly generate settings.gradle with enableFeaturePreview

Previously enableFeaturePreview was ignored for single project build.

This commit fixes them with Gradle version check.

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 1 more file in changeset.
Correctly generate settings.gradle with enableFeaturePreview

Previously enableFeaturePreview was ignored for single project build.

This commit fixes them with Gradle version check.

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 1 more file in changeset.
Correctly generate settings.gradle with enableFeaturePreview

Previously enableFeaturePreview was ignored for single project build.

This commit fixes them with Gradle version check.

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 1 more file 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
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 30 more files in changeset.
Try latest nightly

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 35 more files in changeset.
Try latest nightly

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 35 more files in changeset.
Rebaseline to lock up performance improtments

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 6 more files in changeset.
Lock-in some performance improvements

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 31 more files in changeset.
Rebaseline performance test

A slight regression was introduced by a bugfix release. The

regression is due to slightly more work done when deriving

variants for Maven (creation of implicit capabilities for

platforms).

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
Rebaseline performance tests

There is a small regression due to the introduction of support of

capabilities as dependency selectors (for optional features).

While the branch build didn't fail, merging into master made this

go slightly over the limit.

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 1 more file in changeset.
Rebaseline performance tests

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 30 more files in changeset.
Rebaseline to the same commit to the distribution commit

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 31 more files in changeset.
Rebaseline performance tests

To account for minor regression due to detailed container

callback instrumentation. This information will help find

performance issues that are much bigger than the small overhead

the instrumentation adds.

    • -1
    • +1
    ./ExcludeRuleMergingPerformanceTest.groovy
  1. … 31 more files in changeset.