chore: Update XFails Report

[flashinfer-bot]

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

Summary by CodeRabbit

• Chores
  • Added a test failure summary report containing overall statistics, aggregated failure reasons with counts, detailed per-reason breakdowns with affected test files and conditions, and categorized sections for test environment notes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[gemini-code-assist]

Summary of Changes

Hello @flashinfer-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automatically updates the xfails_report.txt to provide an accurate and current overview of all expected test failures within the project's test suite. This ensures that developers have the latest information on known issues, categorized by reason, to facilitate analysis and potential resolution.

Highlights

• XFails Report Update: The reports/xfails_report.txt file has been updated to reflect the current pytest.mark.xfail markers across the test suite. This report provides a detailed breakdown of 10 xfails across 8 unique reasons, including issues related to SM120/121, CUDA graph, attention sink, seq_len=514 failures, nvidia-cutlass-dsl issues, and numerical accuracy problems.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

📝 Walkthrough

Walkthrough

A new static artifact reports/xfails_report.txt was added containing aggregated pytest xfail data: header totals, a summarized reasons/counts table, and detailed per-reason breakdowns of affected test files, tests, xfail types, and conditions. No executable code changed.

Changes

Cohort / File(s)	Summary
New Report Artifact reports/xfails_report.txt	Added a static xfails report capturing totals, unique reasons, a summarized reasons/counts table, and detailed per-reason breakdowns listing affected test files, test names, xfail types, and conditions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• cicd: add a github workflow for xfails report script #2273: Adds a workflow to generate/update reports/xfails_report.txt automatically (directly related to this artifact).

Suggested reviewers

• jimmyzho
• yongwww

Poem

🐇📋 I hopped through logs by moonlight bright,
Counting xfails one by one tonight,
Reasons like carrots, neat in a row,
I penned their names where cool test-winds blow,
A rabbit guard for tests—soft, steady, light.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: Update XFails Report' directly and clearly describes the main change in the PR, which updates the xfails report artifact.
Description check	✅ Passed	The PR description includes a summary, changes, review guidance, and notes about the automated nature, though it omits the template's description section heading and checklist items.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates the automated xfails report. The report is well-structured, but I've identified one expected failure that uses a non-descriptive reason, str(e). This originates from the test file tests/gemm/test_mm_fp4.py where pytest.xfail is called with a dynamic value. Using a descriptive string literal instead would improve the clarity and utility of this report. My specific comment provides more detail on this.

[gemini-code-assist]

The xfail reason str(e) is not descriptive and makes the report less useful. This is caused by the use of pytest.xfail(str(e)) in tests/gemm/test_mm_fp4.py on line 92. The static analysis script that generates this report cannot resolve the value of str(e) and therefore uses the literal code as the reason.

To improve this, the pytest.xfail call should be updated to use a descriptive string literal. Based on the context in the test file, a more informative reason would be something like:

"cuDNN backend for FP4 GEMM with mxfp4 on SM120+ requires cuDNN 9.14.0+"

This change would make the xfail report more understandable and aid in tracking test failures.