Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Create a new category for slow performance regression tests

    • -1
    • +1
    ./categories/PerformanceRegressionTest.java
    • -0
    • +20
    ./categories/SlowPerformanceRegressionTest.java
  1. … 7 more files in changeset.
Throw UOE for unused methods on MavenBuildExperimentSpec

Those methods shouldn't be called.

    • -2
    • +2
    ./fixture/MavenBuildExperimentSpec.groovy
Extract common code for profiler report generation

    • -29
    • +5
    ./AbstractCrossBuildPerformanceTest.groovy
    • -29
    • +5
    ./AbstractCrossVersionGradleProfilerPerformanceTest.groovy
    • -0
    • +47
    ./results/CompositeDataReporter.java
    • -0
    • +63
    ./results/GradleProfilerReporter.java
Use daemon by default in cross build tests

    • -1
    • +1
    ./fixture/GradleVsMavenPerformanceTestRunner.groovy
  1. … 5 more files in changeset.
Support useDaemon = false

Note that `useDaemon = false` by default for cross build performance

tests.

    • -1
    • +3
    ./fixture/GradleProfilerBuildExperimentRunner.java
Support useDaemon = false

Note that `useDaemon = false` by default for cross build performance

tests.

    • -1
    • +3
    ./fixture/GradleProfilerBuildExperimentRunner.java
Rename AbstractCrossBuild{GradleProfiler -> }PerformanceTest

There is only one.

    • -105
    • +0
    ./AbstractCrossBuildGradleProfilerPerformanceTest.groovy
    • -0
    • +105
    ./AbstractCrossBuildPerformanceTest.groovy
  1. … 8 more files in changeset.
Remove AbstractCrossBuildPerformanceTest

    • -78
    • +0
    ./AbstractCrossBuildPerformanceTest.groovy
Separate Gradle profiler specific options

    • -1
    • +1
    ./fixture/AbstractCrossBuildPerformanceTestRunner.groovy
    • -26
    • +3
    ./fixture/AbstractGradleBuildPerformanceTestRunner.groovy
    • -1
    • +11
    ./fixture/CrossBuildGradleInternalPerformanceTestRunner.groovy
    • -1
    • +24
    ./fixture/CrossBuildGradleProfilerPerformanceTestRunner.groovy
    • -3
    • +3
    ./fixture/GradleBuildExperimentSpec.groovy
    • -0
    • +5
    ./fixture/GradleVsMavenPerformanceTestRunner.groovy
    • -2
    • +20
    ./fixture/MavenBuildExperimentSpec.groovy
Create separate cross build runner class

    • -3
    • +3
    ./AbstractCrossBuildGradleProfilerPerformanceTest.groovy
    • -0
    • +72
    ./fixture/AbstractCrossBuildPerformanceTestRunner.groovy
    • -45
    • +4
    ./fixture/CrossBuildGradleInternalPerformanceTestRunner.groovy
    • -0
    • +30
    ./fixture/CrossBuildGradleProfilerPerformanceTestRunner.groovy
Rename CrossBuild{ -> GradleInternal}PerformanceTestRunner

    • -3
    • +3
    ./AbstractCrossBuildGradleProfilerPerformanceTest.groovy
    • -3
    • +3
    ./AbstractCrossBuildPerformanceTest.groovy
    • -0
    • +71
    ./fixture/CrossBuildGradleInternalPerformanceTestRunner.groovy
    • -71
    • +0
    ./fixture/CrossBuildPerformanceTestRunner.groovy
  1. … 3 more files in changeset.
First working versino

    • -0
    • +105
    ./AbstractCrossBuildGradleProfilerPerformanceTest.groovy
    • -4
    • +2
    ./AbstractCrossBuildPerformanceTest.groovy
    • -4
    • +2
    ./AbstractGradleVsMavenPerformanceTest.groovy
    • -2
    • +22
    ./fixture/AbstractGradleBuildPerformanceTestRunner.groovy
    • -0
    • +10
    ./fixture/BuildExperimentSpec.groovy
    • -2
    • +3
    ./fixture/CrossBuildPerformanceTestRunner.groovy
    • -1
    • +1
    ./fixture/GradleBuildExperimentSpec.groovy
    • -2
    • +3
    ./fixture/GradleVsMavenPerformanceTestRunner.groovy
    • -0
    • +7
    ./fixture/MavenBuildExperimentSpec.groovy
  1. … 4 more files in changeset.
Use unified timestamp when cleaning stale data (#10732)

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

Previously we saw some failures when cleaning stale data. This might be

caused by different timestamps used. This commit uses same timestamp to

clean both testOperation and testExecution table.

    • -4
    • +5
    ./results/StaleDataCleanupInitializer.java
Use unified timestamp when cleaning stale data

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

Previously we saw some failures when cleaning stale data. This might be

cause by different timestamps used. This commit uses same timestamp to

clean both testOperation and testExecution table.

    • -4
    • +5
    ./results/StaleDataCleanupInitializer.java
Use unified timestamp when cleaning stale data

Previously we saw some failures when cleaning stale data. This might be

cause by different timestamps used. This commit uses same timestamp to

clean both testOperation and testExecution table.

    • -4
    • +5
    ./results/StaleDataCleanupInitializer.java
Address review feedback

    • -0
    • +64
    ./results/ScenarioResult.java
    • -1
    • +6
    ./results/report/DefaultPerformanceFlakinessDataProvider.java
    • -6
    • +6
    ./results/report/IndexPageGenerator.java
    • -2
    • +4
    ./results/report/PerformanceFlakinessDataProvider.java
Address review feedback

    • -1
    • +6
    ./results/report/DefaultPerformanceFlakinessDataProvider.java
    • -6
    • +6
    ./results/report/IndexPageGenerator.java
    • -2
    • +4
    ./results/report/PerformanceFlakinessDataProvider.java
Mark small regressions as nearly failed

instead of failed

    • -3
    • +15
    ./results/report/IndexPageGenerator.java
Mark small regressions as nearly failed

instead of failed

    • -2
    • +9
    ./results/report/IndexPageGenerator.java
Mark small regressions as nearly failed

instead of failed

    • -2
    • +9
    ./results/report/IndexPageGenerator.java
Move flakyness type determining to FlakinessDataProvider

    • -0
    • +25
    ./results/report/DefaultPerformanceFlakinessDataProvider.java
    • -16
    • +11
    ./results/report/DefaultReportGenerator.java
    • -0
    • +23
    ./results/report/PerformanceFlakinessDataProvider.java
Move flakyness type determining to FlakinessDataProvider

    • -0
    • +25
    ./results/report/DefaultPerformanceFlakinessDataProvider.java
    • -16
    • +11
    ./results/report/DefaultReportGenerator.java
    • -0
    • +23
    ./results/report/PerformanceFlakinessDataProvider.java
Always print result from report generator

Always print result from report generator

Small polish

    • -2
    • +1
    ./results/report/IndexPageGenerator.java
  1. … 2 more files in changeset.
Small polish

    • -2
    • +1
    ./results/report/IndexPageGenerator.java
  1. … 2 more files in changeset.
Print log

    • -0
    • +2
    ./generator/FileContentGenerator.groovy
Fix enableFeaturePreview failure on template project execution

Fix https://github.com/gradle/gradle/issues/10454

Previously, lower Gradle version might not be able to execute the template project

generated because of it doesn't have some features. This commit fixes it by catching

the exception.

    • -3
    • +8
    ./generator/FileContentGenerator.groovy
Fix Groovy performance project generator for Gradle 4.6-5.5

    • -2
    • +2
    ./generator/FileContentGenerator.groovy
Fix incorrect performance result

    • -11
    • +14
    ./results/report/DefaultPerformanceExecutionDataProvider.java