SwiftBuildPerformanceTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rebaseline `incremental compile on mediumSwiftMulti` as well

This has not been rebaselined, since it was using a version specific

to the test.

Rebaseline performance tests again

  1. … 31 more files in changeset.
Rebaseline performance tests

  1. … 30 more files in changeset.
Rebaseline performance scenarios

  1. … 2 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. … 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. … 25 more files in changeset.
Refine performance baseline selection logic

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

  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. … 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.
Rebaseline SwiftBuildPerformanceTest.incremental compile on bigSwiftApp

Looking at the history, there's a gradual tiny regression. Rebaseline it.

Merge remote-tracking branch 'origin/master-test' into release-test

  1. … 5 more files in changeset.
Merge remote-tracking branch 'origin/master-test' into release-test

  1. … 5 more files in changeset.
Rebaseline some scenarios for release

Looking at the history, some regressions exist before branching. It's pointless to rebaseline master

but not rebaseline release for these scenarios.

  1. … 3 more files 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.
Try latest nightly

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

  1. … 35 more files in changeset.
Rebaseline incremental compile on mediumSwiftMulti

Looking at the history graph, there's a gradual performance regression, rebaseline it.

Lock-in some performance improvements

  1. … 31 more files in changeset.
Remove unused imports

  1. … 1 more file in changeset.
Reenable the Swift performance tests

  1. … 1 more file in changeset.
Ignore failing Swift perf tests

Older versions of Gradle do not support Swift 5

  1. … 2 more files in changeset.
Ignore failing Swift perf tests

Older versions of Gradle do not support Swift 5

  1. … 2 more files in changeset.
Rebaseline performance tests

  1. … 30 more files in changeset.
Rebaseline to the same commit to the distribution commit

  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. … 31 more files in changeset.
Lock in recent performance improvements

  1. … 31 more files in changeset.
Rebaseline performance tests

We introduced a ThreadLocal in the project locking which slowed things

down a little bit (10s of ms) in several builds. Rebaselining to prevent

this from affecting all branches.

  1. … 31 more files in changeset.
Rebaseline performance tests after merging single project lock changes

  1. … 31 more files in changeset.
Rebaseline performance tests

The introduction of the "platform" support introduced a couple small regressions,

but also improvements in some cases. This commit re-enables the Java IDE performance

test now that we have a baseline to compare with. Work on improving performance

is going to happen later.

  1. … 31 more files in changeset.