Skip to content

Skip trtllm_alltoall tests on Thor#2448

Merged
yongwww merged 2 commits intoflashinfer-ai:mainfrom
dierksen:thor-fix
Feb 1, 2026
Merged

Skip trtllm_alltoall tests on Thor#2448
yongwww merged 2 commits intoflashinfer-ai:mainfrom
dierksen:thor-fix

Conversation

@dierksen
Copy link
Contributor

@dierksen dierksen commented Jan 30, 2026

📌 Description

After adding Thor to our internal CI, we've been seeing consistent hangs in this test suite. Since this functionality likely isn't crucial for this platform, we can disable the tests to unblock the rest of the testing and get nightly Thor test results.

🔍 Related Issues

🚀 Pull Request Checklist

Thank you for contributing to FlashInfer! Before we review your pull request, please make sure the following items are complete.

✅ Pre-commit Checks

  • I have installed pre-commit by running pip install pre-commit (or used your preferred method).
  • I have installed the hooks with pre-commit install.
  • I have run the hooks manually with pre-commit run --all-files and fixed any reported issues.

If you are unsure about how to set up pre-commit, see the pre-commit documentation.

🧪 Tests

  • Tests have been added or updated as needed.
  • All tests are passing (unittest, etc.).

Reviewer Notes

Summary by CodeRabbit

  • Tests
    • Updated tests to skip execution on SM110/Thor CUDA devices to prevent hangs during test runs.

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

dierksen and others added 2 commits January 30, 2026 16:48
Add module-level pytest skip for all tests in test_trtllm_alltoall.py
when running on SM110 compute capability devices (Thor). These tests
have known issues on this architecture.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Update comment and skip reason to explicitly state that these tests
hang indefinitely on SM110 (Thor) devices rather than just having
"known issues".

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @dierksen, I'm Gemini Code Assist1! 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 addresses a critical issue in the continuous integration pipeline where trtllm_alltoall tests were causing indefinite hangs on Thor devices. By introducing a conditional skip for these tests on the affected architecture, the PR ensures that the CI can complete successfully, allowing for nightly test results and unblocking further development and testing on the Thor platform. This change improves the reliability and efficiency of the testing infrastructure.

Highlights

  • Test Skipping for Thor Devices: Implemented a mechanism to skip all tests within tests/comm/test_trtllm_alltoall.py specifically for devices with compute capability SM110 (Thor).
  • Addressing CI Hangs: The tests were consistently hanging indefinitely on Thor devices, and skipping them unblocks the continuous integration pipeline for this platform.

🧠 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
Copy link
Contributor

coderabbitai bot commented Jan 30, 2026

📝 Walkthrough

Walkthrough

A test skip marker was added to conditionally bypass all tests in the module when a CUDA device with compute capability 11 (SM110/Thor) is detected, using a new import from flashinfer.utils to prevent test hangs on specific hardware.

Changes

Cohort / File(s) Summary
Test Skip Configuration
tests/comm/test_trtllm_alltoall.py
Added import from flashinfer.utils and introduced pytest skip marker to conditionally bypass all tests when SM110 (Thor) GPU compute capability is detected, preventing hangs on specific hardware.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested reviewers

  • yzh119

Poem

🐰 A skip marker hops with glee,
On SM110 we now run free,
No hangs will plague our testing day,
Thor's hung tests now stay away! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: skipping trtllm_alltoall tests on Thor devices.
Description check ✅ Passed The description provides clear context about why tests are being skipped on Thor due to consistent hangs, but the Tests checklist items remain unchecked despite modifying test behavior.
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.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

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

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request disables the trtllm_alltoall tests on Thor (SM110) devices where they are known to hang. The change is correct and uses pytest.mark.skipif appropriately. I've added one suggestion to improve the robustness of the test skipping logic by also handling cases where CUDA is not available, which would currently lead to test failures instead of skips.

Comment on lines +23 to +28
# Skip all tests on SM110 (Thor) devices - these tests hang indefinitely on this architecture
pytestmark = pytest.mark.skipif(
torch.cuda.is_available()
and get_compute_capability(torch.device("cuda:0"))[0] == 11,
reason="Tests hang indefinitely on SM110 (Thor) devices",
)
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The current implementation correctly skips tests on Thor devices. However, if CUDA is not available, the skipif condition evaluates to false, causing the tests to run and subsequently fail because they require CUDA. It is better practice for tests to be skipped if their environmental requirements are not met.

This suggestion refactors the logic to also skip all tests in this file if CUDA is not available. This provides a clearer result for developers running tests in a non-GPU environment and makes the skipping logic more robust and easier to read.

Suggested change
# Skip all tests on SM110 (Thor) devices - these tests hang indefinitely on this architecture
pytestmark = pytest.mark.skipif(
torch.cuda.is_available()
and get_compute_capability(torch.device("cuda:0"))[0] == 11,
reason="Tests hang indefinitely on SM110 (Thor) devices",
)
# Skip all tests on SM110 (Thor) devices and if CUDA is not available
_skip_reason = None
if not torch.cuda.is_available():
_skip_reason = "CUDA not available, skipping trtllm_alltoall tests"
elif get_compute_capability(torch.device("cuda:0"))[0] == 11:
_skip_reason = "Tests hang indefinitely on SM110 (Thor) devices"
pytestmark = pytest.mark.skipif(_skip_reason is not None, reason=_skip_reason)

Copy link
Collaborator

Choose a reason for hiding this comment

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

CUDA will always be available when we test FlashInfer

@bkryu
Copy link
Collaborator

bkryu commented Jan 30, 2026

/bot run

@flashinfer-bot
Copy link
Collaborator

GitLab MR !282 has been created, and the CI pipeline #42938127 is currently running. I'll report back once the pipeline job completes.

@flashinfer-bot
Copy link
Collaborator

[FAILED] Pipeline #42938127: 6/20 passed

@yzh119
Copy link
Collaborator

yzh119 commented Feb 1, 2026

@flashinfer-bot run

@yongwww
Copy link
Member

yongwww commented Feb 1, 2026

@flashinfer-bot rerun failed

@yongwww yongwww merged commit 5d5e164 into flashinfer-ai:main Feb 1, 2026
62 of 67 checks passed
nv-yunzheq pushed a commit to nv-yunzheq/flashinfer that referenced this pull request Feb 2, 2026
<!-- .github/pull_request_template.md -->

## 📌 Description

After adding Thor to our internal CI, we've been seeing consistent hangs
in this test suite. Since this functionality likely isn't crucial for
this platform, we can disable the tests to unblock the rest of the
testing and get nightly Thor test results.

## 🔍 Related Issues

<!-- Link any related issues here -->

## 🚀 Pull Request Checklist

Thank you for contributing to FlashInfer! Before we review your pull
request, please make sure the following items are complete.

### ✅ Pre-commit Checks

- [x] I have installed `pre-commit` by running `pip install pre-commit`
(or used your preferred method).
- [x] I have installed the hooks with `pre-commit install`.
- [x] I have run the hooks manually with `pre-commit run --all-files`
and fixed any reported issues.

> If you are unsure about how to set up `pre-commit`, see [the
pre-commit documentation](https://pre-commit.com/).

## 🧪 Tests

- [ ] Tests have been added or updated as needed.
- [ ] All tests are passing (`unittest`, etc.).

## Reviewer Notes

<!-- Optional: anything you'd like reviewers to focus on, concerns, etc.
-->


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Tests**
* Updated tests to skip execution on SM110/Thor CUDA devices to prevent
hangs during test runs.

<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
raayandhar pushed a commit to raayandhar/flashinfer that referenced this pull request Feb 5, 2026
<!-- .github/pull_request_template.md -->

## 📌 Description

After adding Thor to our internal CI, we've been seeing consistent hangs
in this test suite. Since this functionality likely isn't crucial for
this platform, we can disable the tests to unblock the rest of the
testing and get nightly Thor test results.

## 🔍 Related Issues

<!-- Link any related issues here -->

## 🚀 Pull Request Checklist

Thank you for contributing to FlashInfer! Before we review your pull
request, please make sure the following items are complete.

### ✅ Pre-commit Checks

- [x] I have installed `pre-commit` by running `pip install pre-commit`
(or used your preferred method).
- [x] I have installed the hooks with `pre-commit install`.
- [x] I have run the hooks manually with `pre-commit run --all-files`
and fixed any reported issues.

> If you are unsure about how to set up `pre-commit`, see [the
pre-commit documentation](https://pre-commit.com/).

## 🧪 Tests

- [ ] Tests have been added or updated as needed.
- [ ] All tests are passing (`unittest`, etc.).

## Reviewer Notes

<!-- Optional: anything you'd like reviewers to focus on, concerns, etc.
-->


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Tests**
* Updated tests to skip execution on SM110/Thor CUDA devices to prevent
hangs during test runs.

<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants