Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Allow using Gradle profiler in cross version tests

  1. … 12 more files in changeset.
Allow using Gradle profiler in cross version tests

  1. … 11 more files in changeset.
Allow using Gradle profiler in cross version tests

  1. … 12 more files in changeset.
Allow using Gradle profiler in cross version tests

  1. … 12 more files in changeset.
Mark known flaky performance test in report (#8997)

This closes https://github.com/gradle/gradle-private/issues/1735

We want to mark the known performance test scenarios in the report even when they pass. This can give us insights of how the scenarios work previously. In this way, we can easily know, "this scenario fails, ah, it's marked as flaky", or, "this scenario is improved, but hold on, it's marked as flaky, let's not rebaseline it".

  1. … 13 more files in changeset.
Do not use singleton pattern for FlakinessAnalyzer

A field is just as good.

  1. … 6 more files in changeset.
Do not use singleton patter for FlakinessAnalyzer

A field is just as good.

  1. … 6 more files in changeset.
Detect flaky performance test scenarios (#8367)

As part of https://github.com/gradle/gradle-private/issues/1635 , we want to detect flaky performance test with a weekly job, in order to know which scenarios are flaky.

  1. … 22 more files in changeset.
Add teamcity build id to performance tests (#7524)

This fixes https://github.com/gradle/gradle-private/issues/1535

Previously, we only don't have buildId recorded in performance database, which might cause incorrect result if running multiple performance builds against same commit. This PR adds `teamCityBuildId` column to performance test database.

A bonus is that we now have build url link in performance graph page.

  1. … 17 more files in changeset.
Make the build scan plugin perf test project smaller, but run more iterations

This should hopefully help produce more stable results

  1. … 2 more files in changeset.
Extract plugin application logic out of template generation

+review REVIEW-6596

  1. … 3 more files in changeset.
Reset warmup and measured build for build scan performance tests

  1. … 1 more file in changeset.
Introduce experimental performance build testing per file input hashes

    • -0
    • +90
    ./org/gradle/performance/AbstractBuildScanPluginPerformanceTest.groovy
  1. … 3 more files in changeset.
Strive to keep Gradle's monotonic clock in sync with the system clock

  1. … 71 more files in changeset.
Add host name to performance test results

  1. … 15 more files in changeset.
Break up package cycle by moving Git util to own package

  1. … 8 more files in changeset.
Wire integration test build context instance

- enables using performance test specific build context when an instance

is properly wired

  1. … 48 more files in changeset.
Fix startTime and endTime in performance tests

- broke by 1b20ea8d

  1. … 5 more files in changeset.
Add TimeProvider.currentTimeForDuration and use it

There were many places we were measuring a duration by comparing

`System.currentTimeMillis()` at some start and end times. This is a

known anti-pattern which is subject to incorrect duration measurements

due to how clock skew affects the implementation of that function.

The new `currentTimeForDuration()` method uses `System.nanoTime()` which

is much more reliable for measuring durations within a single thread of

control in a single process.

Replacing our uses of `System.currentTimeMillis()` with

`currentTimeForDuration()` will make Gradle and our tests much more

reliable.

In service of issue #740

  1. … 37 more files in changeset.
Add `channel` to the performance test execution database

The `channel` column introduced by this commit allows us to put the tests into different

"channels", where a channel corresponds to a type of build: daily, commit by commit builds

(the default `commits` channel), ad-hoc builds (`adhoc`) or historical builds (`historical`).

The channel is controlled thanks to the `org.gradle.performance.execution.channel` system

property.

  1. … 20 more files in changeset.
Correct estimated runtime calculation

  1. … 19 more files in changeset.
Move all result-related classes to org.gradle.performance.results

  1. … 54 more files in changeset.
Use a fresh results store for build scan performance results.

Allow connecting to a remote performance test database

This change makes it possible to specify a remote H2 database url, username and password

on the command line using the properties

org.gradle.performance.db.url

org.gradle.performance.db.username

org.gradle.performance.db.password

The default behavior remains as before: Using a folder in the user's home directory.

  1. … 10 more files in changeset.
Revert "Allow connecting to a remote performance test database"

This reverts commit 75afd979bd658ff05cdb55d0f78ff32a64a461fa.

  1. … 7 more files in changeset.
Allow connecting to a remote performance test database

This change makes it possible to specify a remote H2 database url, username and password

on the command line using the properties

org.gradle.performance.db.url

org.gradle.performance.db.username

org.gradle.performance.db.password

The default behavior remains as before: Using a folder in the user's home directory.

  1. … 7 more files in changeset.
Move Build Scan performance test to own project

    • -0
    • +29
    ./org/gradle/performance/results/BuildScanResultsStore.java
  1. … 27 more files in changeset.