PerformanceTestCoordinator.kt

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix warnings

  1. … 1 more file in changeset.
Adjust teamcity configuration

  1. … 2 more files in changeset.
Adjust teamcity configuration

  1. … 2 more files in changeset.
New performance process (#10361)

This PR introduces new performance test process. See more details in https://docs.google.com/document/u/1/d/1pghuxbCR5oYWhUrIK2e4bmABQt3NEIYOOIK4iHyjWyQ/edit#heading=h.is4fzcbmxxld

  1. … 50 more files in changeset.
Make error message more friendly

  1. … 4 more files in changeset.
Make error message more friendly

  1. … 4 more files in changeset.
Don't tag the build by tagging plugin

  1. … 2 more files in changeset.
Publish Github status for non-functional test builds

All those are sufficiently interesting to show as Github check.

  1. … 8 more files in changeset.
Automatically format code

  1. … 15 more files in changeset.
Automatically format code

  1. … 15 more files in changeset.
Move Kotlin DSL code to settings

  1. … 99 more files in changeset.
Revert "Correct the rerun property"

This reverts commit 1f1d91b3d54cdae05dd35ffad40b9fad786e624b.

  1. … 4 more files in changeset.
Revert "Correct the rerun property"

This reverts commit 1f1d91b3d54cdae05dd35ffad40b9fad786e624b.

  1. … 4 more files in changeset.
Correct the rerun property

  1. … 4 more files in changeset.
Correct the rerun property

  1. … 4 more files in changeset.
Pass Github token to flakiness detection build (#8967)

The build to determine performance test flakiness wants to open Github

issues as well.

  1. … 2 more files in changeset.
Always pass Github API token

  1. … 3 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`.

    • -0
    • +67
    ./PerformanceTestCoordinator.kt
  1. … 23 more files in changeset.
Rebase to latest master

  1. … 23 more files in changeset.
Set build scan tag via system property

  1. … 5 more files in changeset.
Resolve feedbacks

    • -0
    • +66
    ./PerformanceTestCoordinator.kt
  1. … 5 more files in changeset.