[Issue]: UT test_moe.py stuck with certain problem size
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 565
- Forks
- 585
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 366
Description
Problem Description
UT test_moe.py stuck with certain problem size
test_fmoe(torch.float16, 8192, 2048, 1664, 96, 8, quant="No")
Operating System
ID_LIKE="rhel fedora centos anolis"
CPU
Intel(R) Xeon(R) Platinum 8469C
GPU
AMD Instinct MI308X
ROCm Version
ROCm 6.3.3
ROCm Component
No response
Steps to Reproduce
python aiter/op_tests/test_moe.py
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Run python aiter/op_tests/test_moe.py and reproduce the hang with test_fmoe(torch.float16, 8192, 2048, 1664, 96, 8, quant="No") on the reported ROCm and AMD GPU environment. Investigate why this case does not complete and verify that the test finishes successfully without regressing other test_moe.py cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100