performance

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Run tests on the JUnit Platform using Spock 2.0

  1. … 5 more files in changeset.
Try increasing performance test memory

  1. … 3 more files in changeset.
Fetch flakiness data

  1. … 5 more files in changeset.
Add missing type information to `PerformanceTestPlugin`

For compatibility with Kotlin 1.3.41.

Change all subprojects to use 'implementation' dependencies

This includes:

- All projects now explicitly declare all dependencies to other

subprojects. This makes issues more visible, guards for accidental

addition of new dependencies, and leaks much less transitive

dependencies on the compile classpathes.

- All usages of 'runtime' to declare dependencies have been replaced

with 'runtimeOnly'

- All projects are now `java-library` (and declare this explicitly)

- Most remaining Groovy scripts are translated to Kotlin

- The old 'compile' and 'runtime' configurations are not

configured/created anymore for the 'testFixture' and 'integTest'

source sets.

- Some obsolete dependencies (see previous commits) are removed

- 'api' is used scarcely on purpose as the current project structure is

not well designed for this. The projects contain code for several

concerns of the build tool and thus putting complete projects on the

API of others exposes too much. They should be split up along

functional concerns first.

  1. … 112 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 286 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 283 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 286 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 284 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 285 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 285 more files in changeset.
Rerun distributed performance test in RERUNNER step (#8801)

After the improvement of automatically rerunning and tagging, we want to manage performance test in the same way:

- Only run each performance test scenario once.

- If it fails, `GRADLE_RERUNNER` will kick in and rerun the failed scenario. The good thing is that it might be scheduled to another build agent, which mitigates the effect of bad agent.

This PR does:

- Remove all `Retry` from performance tests.

- Add `GRADLE_RERUNNER` to performance tests and refactor some code.

- Add tests for `PerformanceTest`.

- Since `GRADLE_RERUNNER` depends on reading of test binary result, write binary test result file in `RerunableDistributedPerformanceTest`.

  1. … 23 more files in changeset.
Rebase to latest master

  1. … 23 more files in changeset.
Handle rerun performance test

  1. … 7 more files in changeset.
Handle rerun performance test

  1. … 7 more files in changeset.
Handle rerun performance test

  1. … 8 more files in changeset.
Handle rerun performance test

  1. … 8 more files in changeset.
Handle rerun performance test

  1. … 8 more files in changeset.
Handle rerun performance test

  1. … 7 more files in changeset.
Handle rerun performance test

  1. … 7 more files in changeset.
Handle rerun performance test

  1. … 8 more files in changeset.
Test rerun

  1. … 3 more files in changeset.
Test rerun

  1. … 2 more files in changeset.
Test rerun

  1. … 3 more files in changeset.
Fix cache-hit in flakiness detection performance test (#8482)

We don't want build cache hit in performance flakiness detection, however, previously the coordinator build resolves "flakiness-detection-commit" baseline to real commit id "5.3-commit-237a600", resulting in unexpected cache hit.

This PR fixes it by:

- On coordinator's side, pass "flakiness-detection-commit" as it is to worker build.

- On worker's side, worker build resolves "flakiness-detection-commit" to real commit version - this disables build cache.

Since `DetermineBaselines` is becoming more and more complex, this PR also adds a unit test for `DetermineBaselines` class.

  1. … 3 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. … 21 more files in changeset.
fix issue

  1. … 1 more file in changeset.
Disable fork point commit detection

Disable fork point commit detection

Fetch branch name from environment variable when necessary (#7947)

Previously we use JGit's branch, which might be not accurate.

Now we prefer environment variable over JGit.

  1. … 3 more files in changeset.