Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions .github/workflows/update-codeowners.yml
100644 β†’ 100755
Original file line number Diff line number Diff line change
Expand Up @@ -73,10 +73,6 @@ jobs:
chore: update CODEOWNERS based on git history

Auto-generated CODEOWNERS update based on commit activity over the last ${{ env.DAYS_BACK }} days.

πŸ€– Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
branch: auto-update-codeowners
base: main
delete-branch: true
Expand Down
102 changes: 102 additions & 0 deletions .github/workflows/update-xfails-report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,102 @@
name: Update XFails Report

on:
schedule:
# Run weekly on Monday at 00:00 UTC
- cron: '0 0 * * 1'
workflow_dispatch: # Allow manual triggering

permissions:
contents: write
pull-requests: write

jobs:
update-xfails-report:
runs-on: ubuntu-latest
timeout-minutes: 30
steps:
- name: Checkout repository
uses: actions/checkout@v4.2.2
with:
fetch-depth: 1 # Shallow clone is sufficient for scanning test files
token: ${{ secrets.GITHUB_TOKEN }}
Comment on lines +18 to +22
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

latest version of actions/checkout GitHub Action 2025

πŸ’‘ Result:

The latest major version is v6 β€” use actions/checkout@v6. [1][2]

Sources:
[1] actions/checkout GitHub repository README.
[2] Checkout page on the GitHub Marketplace.


Update actions/checkout to the latest version.

The version v4.2.2 is outdated. The latest stable version is v6. Update to actions/checkout@v6 to ensure security patches and bug fixes are included.

πŸ€– Prompt for AI Agents
.github/workflows/update-xfails-report.yml around lines 18 to 22: the workflow
pins actions/checkout to v4.2.2 which is outdated; update the action reference
to actions/checkout@v6 by replacing the version string so the workflow uses the
latest stable v6 release, keeping the existing with: block (fetch-depth and
token) intact.


- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: '3.11'

- name: Create reports directory
run: mkdir -p reports

- name: Run XFails tracker
run: |
python scripts/xfails_tracker.py > reports/xfails_report.txt 2>&1 || {
echo "Error: XFails tracker script failed"
cat reports/xfails_report.txt
exit 1
}

- name: Check for changes
id: check_changes
run: |
# Check if xfails report file is new (unstaged) or has changes
if git ls-files --error-unmatch reports/xfails_report.txt >/dev/null 2>&1; then
# File is tracked, check for changes
if git diff --quiet reports/xfails_report.txt; then
echo "changed=false" >> $GITHUB_OUTPUT
echo "No changes detected in xfails report"
else
echo "changed=true" >> $GITHUB_OUTPUT
echo "Changes detected in xfails report"
fi
else
# File is untracked (newly created)
echo "changed=true" >> $GITHUB_OUTPUT
echo "XFails report file is new"
fi

- name: Create Pull Request
if: steps.check_changes.outputs.changed == 'true'
uses: peter-evans/create-pull-request@v7
with:
token: ${{ secrets.FLASHINFER_BOT_TOKEN }}
committer: flashinfer-bot <flashinfer-bot@users.noreply.github.com>
author: flashinfer-bot <flashinfer-bot@users.noreply.github.com>
commit-message: |
chore: update xfails report

Auto-generated xfails report based on current test suite markers.
branch: auto-update-xfails-report
base: main
delete-branch: true
title: 'chore: Update XFails Report'
body: |
## Summary

This PR updates the xfails report based on the current test suite.

## Changes

- Updated `reports/xfails_report.txt` with current xfail markers from the test suite

## How to Review

1. Review the changes to `reports/xfails_report.txt`
2. Check if the number of xfails has increased or decreased
3. Review the reasons for any new xfails
4. Consider addressing xfails that may no longer be needed

## Notes

- This is an automated PR generated weekly
- The report shows all `pytest.mark.xfail` markers in the test suite
- Grouped by reason for easy analysis

---

πŸ€– This PR was automatically generated by the [update-xfails-report workflow](.github/workflows/update-xfails-report.yml)
labels: |
automated
maintenance
testing
Comment on lines +59 to +102
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟑 Minor

🧩 Analysis chain

🌐 Web query:

peter-evans/create-pull-request latest version GitHub Action

πŸ’‘ Result:

The latest major release is v8 β€” use peter-evans/create-pull-request@v8 (you can pin to a specific patch like @v8.x.x). [1][2]

Sources:
[1] GitHub repo README (peter-evans/create-pull-request).
[2] GitHub Marketplace entry for Create Pull Request.


Upgrade peter-evans/create-pull-request to v8.

Update the action version from @v7 to @v8, which is the latest major release. The rest of the PR creation step is well-structured with appropriate bot attribution, comprehensive PR body, and automatic branch cleanup.

πŸ€– Prompt for AI Agents
.github/workflows/update-xfails-report.yml around lines 59 to 106: the workflow
uses peter-evans/create-pull-request@v7 and needs to be upgraded to @v8; update
the uses line to reference peter-evans/create-pull-request@v8 and ensure any
breaking-change inputs required by v8 are handled (verify token, committer,
author, commit-message, branch, base, delete-branch, title, body, and labels
inputs remain valid in v8 and adjust names or formats if the action changed
them).