Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Run santa tracker Java as well

  1. … 4 more files in changeset.
all reruns

  1. … 4 more files in changeset.
Run santa tracker Java as well

  1. … 4 more files in changeset.
Run santa tracker Java as well

  1. … 4 more files in changeset.
Allow easier adding of build mutator for cross build tests

  1. … 1 more file in changeset.
Allow easier adding of build mutator for cross build tests

  1. … 1 more file in changeset.
Allow easier adding of build mutator for cross build tests

  1. … 1 more file in changeset.
Fix hierarchy for PerformanceExperiment

A performance experiment is not a performance regression test.

Create a new category for slow performance regression tests

  1. … 7 more files in changeset.
Throw UOE for unused methods on MavenBuildExperimentSpec

Those methods shouldn't be called.

Extract common code for profiler report generation

    • -0
    • +47
    ./groovy/org/gradle/performance/results/CompositeDataReporter.java
Use daemon by default in cross build tests

  1. … 5 more files in changeset.
Support useDaemon = false

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

tests.

Support useDaemon = false

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

tests.

Rename AbstractCrossBuild{GradleProfiler -> }PerformanceTest

There is only one.

  1. … 8 more files in changeset.
Remove AbstractCrossBuildPerformanceTest

Separate Gradle profiler specific options

Create separate cross build runner class

Rename CrossBuild{ -> GradleInternal}PerformanceTestRunner

  1. … 3 more files in changeset.
First working versino

    • -0
    • +105
    ./groovy/org/gradle/performance/AbstractCrossBuildGradleProfilerPerformanceTest.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.

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.

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.

Address review feedback

    • -0
    • +64
    ./groovy/org/gradle/performance/results/ScenarioResult.java
Address review feedback

Mark small regressions as nearly failed

instead of failed

Mark small regressions as nearly failed

instead of failed

Mark small regressions as nearly failed

instead of failed

Move flakyness type determining to FlakinessDataProvider

Move flakyness type determining to FlakinessDataProvider