This is an automated email from the ASF dual-hosted git repository.

alamb pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/datafusion.git


The following commit(s) were added to refs/heads/main by this push:
     new 1164a37262 Remove pr_benchmarks.yml (#11165)
1164a37262 is described below

commit 1164a372627ff62dbd02590995e1aa0482d8a81e
Author: Andrew Lamb <[email protected]>
AuthorDate: Sat Jun 29 16:08:07 2024 -0400

    Remove pr_benchmarks.yml (#11165)
---
 .github/workflows/pr_benchmarks.yml | 101 ------------------------------------
 1 file changed, 101 deletions(-)

diff --git a/.github/workflows/pr_benchmarks.yml 
b/.github/workflows/pr_benchmarks.yml
deleted file mode 100644
index 5827c42e85..0000000000
--- a/.github/workflows/pr_benchmarks.yml
+++ /dev/null
@@ -1,101 +0,0 @@
-# Runs the benchmark command on the PR and
-# on the branch, posting the results as a comment back the PR
-name: Benchmarks
-
-on:
-  issue_comment:
-
-jobs:
-  benchmark:
-    name: Run Benchmarks
-    runs-on: ubuntu-latest
-    if: github.event.issue.pull_request && contains(github.event.comment.body, 
'/benchmark')
-    steps:
-      - name: Dump GitHub context
-        env:
-          GITHUB_CONTEXT: ${{ toJSON(github) }}
-        run: echo "$GITHUB_CONTEXT"
-
-      - name: Checkout PR changes
-        uses: actions/checkout@v4
-        with:
-          ref: refs/pull/${{ github.event.issue.number }}/head
-
-      - name: Setup test data
-        # Workaround for `the input device is not a TTY`, appropriated from 
https://github.com/actions/runner/issues/241
-        shell: 'script -q -e -c "bash -e {0}"'
-        run: |
-          cd benchmarks
-          mkdir data
-          
-          # Setup the TPC-H data sets for scale factors 1 and 10
-          ./bench.sh data tpch
-          ./bench.sh data tpch10
-
-      - name: Generate unique result names
-        run: |
-          echo "HEAD_LONG_SHA=$(git log -1 --format='%H')" >> "$GITHUB_ENV" 
-          echo "HEAD_SHORT_SHA=$(git log -1 --format='%h' --abbrev=7)" >> 
"$GITHUB_ENV" 
-          echo "BASE_SHORT_SHA=$(echo "${{ github.sha }}" | cut -c1-7)" >> 
"$GITHUB_ENV"
-
-      - name: Benchmark PR changes
-        env:
-          RESULTS_NAME: ${{ env.HEAD_SHORT_SHA }}
-        run: |
-          cd benchmarks
-
-          ./bench.sh run tpch
-          ./bench.sh run tpch_mem
-          ./bench.sh run tpch10
-          
-          # For some reason this step doesn't seem to propagate the env var 
down into the script
-          if [ -d "results/HEAD" ]; then
-            echo "Moving results into ${{ env.HEAD_SHORT_SHA }}"
-            mv results/HEAD results/${{ env.HEAD_SHORT_SHA }}
-          fi
-
-      - name: Checkout base commit
-        uses: actions/checkout@v4
-        with:
-          ref: ${{ github.sha }}
-          clean: false
-
-      - name: Benchmark baseline and generate comparison message
-        env:
-          RESULTS_NAME: ${{ env.BASE_SHORT_SHA }}
-        run: |
-          cd benchmarks
-
-          ./bench.sh run tpch
-          ./bench.sh run tpch_mem
-          ./bench.sh run tpch10
-          
-          echo ${{ github.event.issue.number }} > pr
-          
-          pip3 install rich
-          cat > message.md <<EOF
-          # Benchmark results
-          
-          <details>
-          <summary>Benchmarks comparing ${{ github.sha }} (main) and ${{ 
env.HEAD_LONG_SHA }} (PR)</summary>
-
-          \`\`\`
-          $(./bench.sh compare ${{ env.BASE_SHORT_SHA }} ${{ 
env.HEAD_SHORT_SHA }})
-          \`\`\`
-
-          </details>
-          EOF
-          
-          cat message.md
-
-      - name: Upload benchmark comparison message
-        uses: actions/upload-artifact@v4
-        with:
-          name: message
-          path: benchmarks/message.md
-
-      - name: Upload PR number
-        uses: actions/upload-artifact@v4
-        with:
-          name: pr
-          path: benchmarks/pr


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to