[ {
  "scenario" : "org.gradle.performance.experiment.declarativedsl.DeclarativeDslConfigurationPerformanceTest.configure",
  "durations" : [ {
    "testProject" : "largeEmptyMultiProjectDeclarativeDsl",
    "linux" : 350,
    "windows" : 828,
    "macOs" : 229
  } ]
}, {
  "scenario" : "org.gradle.performance.experiment.declarativedsl.DeclarativeDslFirstUsePerformanceTest.clean checkout",
  "durations" : [ {

name: Cleanup stale performance test data

on:
  schedule:
    - cron: '0 4 * * 1'  # Run every Monday at 4:00 AM UTC
  workflow_dispatch:

permissions:
  contents: read
  id-token: write

jobs:
  cleanup-stale-performance-data:
    runs-on: ubuntu-latest

    if: github.repository == 'gradle/gradle'

    steps:
      - name: Checkout repository
        uses: actions/checkout@v6
      

      env:
        # Exclude some projects and configurations that should not contribute to the dependency graph
        DEPENDENCY_GRAPH_EXCLUDE_PROJECTS: ':docs|:internal-performance-testing|:enterprise-plugin-performance|:performance|:internal-integ-testing'

closed, up to a conservative limit, to allow better connection reuse. For most
programs, this change should be a no-op, or result in a performance improvement.
In rare cases, programs that do not benefit from connection reuse might
experience performance degradation if they had been improperly allowing an
excessive amount of idle connections to linger; usually by setting

      - name: Update performance-test-durations.json
        run: |
          ./gradlew performance:writePerformanceTimes -Porg.gradle.performance.db.url=${{ env.PERFORMANCE_DB_URL }} -Porg.gradle.performance.db.username=${{ env.PERFORMANCE_DB_USERNAME }}
      - name: Create Pull Request
        uses: peter-evans/create-pull-request@v8
        with:
          commit-message: Update performance test durations

        name = "AdHoc Performance Scenario - ${os.asName()} ${arch.asName()}"
        id(id)

        applyPerformanceTestSettings(os = os, arch = arch, timeout = 420)
        setArtifactRules(INDIVIDUAL_PERFORAMCE_TEST_ARTIFACT_RULES)

        params {
            text(
                "performance.baselines",
                "",
                display = ParameterDisplay.PROMPT,

                )
                buildReportTab("Incubating APIs Report", "incubation-reports/all-incubating.html")
            }
            if (stage.performanceTests.isNotEmpty()) {
                buildReportTab("Performance", "performance-test-results.zip!report/index.html")
            }
        }

        specificBuildTypes =
            stage.specificBuilds.map {
                it.create(model, stage, FlakyTestStrategy.EXCLUDE)

    long result = 0;
    // Due to the way we shift, we can stop iterating once we've run out of data, the rest
    // of the result already being filled with zeros.

    // This loop is critical to performance, so please check HashBenchmark if altering it.
    int limit = min(length, 8);
    for (int i = 0; i < limit; i++) {
      // Shift value left while iterating logically through the array.

          "name": "TestDistribution"
        }
      },
      {
        "subprojects": [
          "build-cache-spi",
          "build-configuration",
          "execution",
          "internal-performance-testing",
          "jvm-services",
          "launcher",
          "publish",
          "resources",
          "resources-http",
          "unit-test-fixtures",
          "wrapper-shared"
        ],

            <option value="$PROJECT_DIR$/testing/internal-integ-testing" />
            <option value="$PROJECT_DIR$/testing/internal-performance-testing" />
            <option value="$PROJECT_DIR$/testing/internal-testing" />
            <option value="$PROJECT_DIR$/testing/performance" />
            <option value="$PROJECT_DIR$/testing/precondition-tester" />
            <option value="$PROJECT_DIR$/testing/public-api-tests" />