From 2e0117402e7ea5ee5d2351b61aa5c02f5fe4ae71 Mon Sep 17 00:00:00 2001 From: Alex Lunev Date: Thu, 27 Jan 2022 06:46:57 -0800 Subject: [PATCH] workflow: add a stale issue bot for KV test failures KV receives the bulk of roachtest and unit test falures. To deal with this issue we have institued a new triage process for all test failures. As part of the process we want to aggresively remove flakes and old failures that are no longer relevant. This bot will auto-close all KV test-failures (except skipped tests) after 35 days of inactivity. Release note: None --- .github/workflows/kv-test-failure-stale.yml | 34 +++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 .github/workflows/kv-test-failure-stale.yml diff --git a/.github/workflows/kv-test-failure-stale.yml b/.github/workflows/kv-test-failure-stale.yml new file mode 100644 index 000000000000..0a88b3ade52f --- /dev/null +++ b/.github/workflows/kv-test-failure-stale.yml @@ -0,0 +1,34 @@ +name: Mark stale test failure issues for KV + +on: + schedule: + - cron: "0 10 * * 1-4" + workflow_dispatch: + +jobs: + stale: + runs-on: ubuntu-latest + permissions: + issues: write + pull-requests: write + steps: + - uses: actions/stale@v3 + with: + operations-per-run: 1000 + repo-token: ${{ secrets.GITHUB_TOKEN }} + stale-issue-message: | + We have marked this test failure issue as stale because it has been + inactive for 1 month. If this failure is still relevant, removing the + stale label or adding a comment will keep it active. Otherwise, + we'll close it in 5 days to keep the test failure queue tidy. + stale-pr-message: 'Stale pull request message' + stale-issue-label: 'no-test-failure-activity' + stale-pr-label: 'no-pr-activity' + close-issue-label: 'X-stale' + close-pr-label: 'X-stale' + # Disable this for PR's, by setting a very high bar + days-before-pr-stale: 99999 + days-before-issue-stale: 30 + days-before-close: 5 + only-labels: 'T-kv,C-test-failure' + exempt-issue-labels: 'skipped-test'