!1836 merge all_ut into main
feat(ssbuf): add ut for AddControlFlowCondition pass
Created-by: ma_journey
Commit-by: m-everglow
Merged-by: ascend-robot
Description: 动态CV控制：添加AddControlFlowCondition控制流部分的UT
<!---
The core Triton is a small number of people, and we receive many PRs (thank
you!). To help us review your code more quickly, **if you are a new
contributor (less than 3 PRs merged) we ask that you complete the following
tasks and include the filled-out checklist in your PR description.**
Complete the following tasks before sending your PR, and replace [ ] with
[x] to indicate you have done them.
-->
# New contributor declaration
- [ ] I am not making a trivial change, such as fixing a typo in a comment.
- [ ] I have written a PR description following these
[rules](https://cbea.ms/git-commit/#why-not-how).
- [ ] I have run pre-commit run --from-ref origin/main --to-ref HEAD.
- Select one of the following.
- [ ] I have added tests.
- /test for lit tests
- /unittest for C++ tests
- /python/test for end-to-end tests
- [ ] This PR does not need a test because FILL THIS IN.
- Select one of the following.
- [ ] I have not added any lit tests.
- [ ] The lit tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices),
including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)
See merge request: Ascend/triton-ascend!1836
test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest
Co-authored-by: jeshd<chengmaofan@huawei.com>
# message auto-generated for no-merge-commit merge:
!1644 merge cases_refactor_for_main into main
test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest
Created-by: jeshd
Commit-by: jeshd
Merged-by: ascend-robot
Description: <!---
The core Triton is a small number of people, and we receive many PRs (thank
you!). To help us review your code more quickly, **if you are a new
contributor (less than 3 PRs merged) we ask that you complete the following
tasks and include the filled-out checklist in your PR description.**
Complete the following tasks before sending your PR, and replace [ ] with
[x] to indicate you have done them.
-->
### Related Issue
https://gitcode.com/Ascend/triton-ascend/issues/396
### Summary
This PR mainly organizes the examples in the Ascend tutorial into pytest cases, and migrates the original examples to unittest.
### Changes
Added test cases for low-memory dropout, extern functions, grouped gemm, persistent matmul, etc. Meanwhile, converted the corresponding test cases under the tutorial directory to pytest format, keeping them consistent with the original tutorial examples.
Fixed test failures in fused-softmax, matrix-multiplication, demo-libentry, rab_time, hstu_attention and other test cases.
For each test script name.py in third_party/ascend/tutorials, there is a corresponding pytest test case script test_name.py in third_party/ascend/unittest/pytest_ut.
- [x] I am not making a trivial change, such as fixing a typo in a comment.
- [x] I have written a PR description following these
[rules](https://cbea.ms/git-commit/#why-not-how).
- [x] I have run pre-commit run --from-ref origin/main --to-ref HEAD.
- Select one of the following.
- [ ] I have added tests.
- /test for lit tests
- /unittest for C++ tests
- /python/test for end-to-end tests
- [x] This PR does not need a test because fix test cases.
- Select one of the following.
- [x] I have not added any lit tests.
- [ ] The lit tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices),
including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)
See merge request: Ascend/triton-ascend!1644
fix: Handle Name node only when parsing split axis with func in BinOp
Co-authored-by: wutianyao<wutianyao1@huawei.com>
# message auto-generated for no-merge-commit merge:
!1553 merge main2 into main
fix: Handle Name node only when parsing split axis with func in BinOp
Created-by: wutianyao
Commit-by: wutianyao
Merged-by: ascend-robot
Description: The core Triton is a small number of people, and we receive many PRs (thank
you!). To help us review your code more quickly, **if you are a new
contributor (less than 3 PRs merged) we ask that you complete the following
tasks and include the filled-out checklist in your PR description.**
Complete the following tasks before sending your PR, and replace [ ] with
[x] to indicate you have done them.
- [ ] I am not making a trivial change, such as fixing a typo in a comment.
- [ ] I have written a PR description following these
[rules](https://cbea.ms/git-commit/#why-not-how).
- [ ] I have run pre-commit run --from-ref origin/main --to-ref HEAD.
- Select one of the following.
- [ ] I have added tests.
- /test for lit tests
- /unittest for C++ tests
- /python/test for end-to-end tests
- [ ] This PR does not need a test because FILL THIS IN.
- Select one of the following.
- [ ] I have not added any lit tests.
- [ ] The lit tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices),
including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)
See merge request: Ascend/triton-ascend!1553
test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest
Co-authored-by: jeshd<chengmaofan@huawei.com>
# message auto-generated for no-merge-commit merge:
!1644 merge cases_refactor_for_main into main
test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest
Created-by: jeshd
Commit-by: jeshd
Merged-by: ascend-robot
Description: <!---
The core Triton is a small number of people, and we receive many PRs (thank
you!). To help us review your code more quickly, **if you are a new
contributor (less than 3 PRs merged) we ask that you complete the following
tasks and include the filled-out checklist in your PR description.**
Complete the following tasks before sending your PR, and replace [ ] with
[x] to indicate you have done them.
-->
### Related Issue
https://gitcode.com/Ascend/triton-ascend/issues/396
### Summary
This PR mainly organizes the examples in the Ascend tutorial into pytest cases, and migrates the original examples to unittest.
### Changes
Added test cases for low-memory dropout, extern functions, grouped gemm, persistent matmul, etc. Meanwhile, converted the corresponding test cases under the tutorial directory to pytest format, keeping them consistent with the original tutorial examples.
Fixed test failures in fused-softmax, matrix-multiplication, demo-libentry, rab_time, hstu_attention and other test cases.
For each test script name.py in third_party/ascend/tutorials, there is a corresponding pytest test case script test_name.py in third_party/ascend/unittest/pytest_ut.
- [x] I am not making a trivial change, such as fixing a typo in a comment.
- [x] I have written a PR description following these
[rules](https://cbea.ms/git-commit/#why-not-how).
- [x] I have run pre-commit run --from-ref origin/main --to-ref HEAD.
- Select one of the following.
- [ ] I have added tests.
- /test for lit tests
- /unittest for C++ tests
- /python/test for end-to-end tests
- [x] This PR does not need a test because fix test cases.
- Select one of the following.
- [x] I have not added any lit tests.
- [ ] The lit tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices),
including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)
See merge request: Ascend/triton-ascend!1644
test: move mindspore cases to generalization
Co-authored-by: candyhong<1102229410@qq.com>
# message auto-generated for no-merge-commit merge:
!1453 merge main/fix-test-case into main
test: move mindspore cases to generalization
Created-by: candyhong
Commit-by: candyhong
Merged-by: ascend-robot
Description: ## Summary
1. Move MindSpore test cases from pytest_ut to generalization_cases to improve CI execution efficiency.
2. Adjust the tolerance threshold for matmul in test_sync_block to 3e-2, which falls within an acceptable accuracy range.
3. Temporarily disable kernel test cases in CI due to intermittent RuntimeError issues affecting stability; tests will be re-enabled after fixes are applied.
## CheckList
- [x] I am not making a trivial change, such as fixing a typo in a comment.
- [x] I have written a PR description following these
[rules](https://cbea.ms/git-commit/#why-not-how).
- [x] I have run pre-commit run --from-ref origin/main --to-ref HEAD.
- Select one of the following.
- [ ] I have added tests.
- /test for lit tests
- /unittest for C++ tests
- /python/test for end-to-end tests
- [x] This PR does not need a test because FILL THIS IN.
- Select one of the following.
- [x] I have not added any lit tests.
- [ ] The lit tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices),
including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)
See merge request: Ascend/triton-ascend!1453
fix(docs): correct some documents
Co-authored-by: KanuaK<zhouyihan1@huawei.com>
# message auto-generated for no-merge-commit merge:
!1665 merge fix/docs-fix into main
fix(docs): correct some documents
Created-by: KanuaK
Commit-by: KanuaK
Merged-by: ascend-robot
Description: <!---
The core Triton is a small number of people, and we receive many PRs (thank
you!). To help us review your code more quickly, **if you are a new
contributor (less than 3 PRs merged) we ask that you complete the following
tasks and include the filled-out checklist in your PR description.**
Complete the following tasks before sending your PR, and replace [ ] with
[x] to indicate you have done them.
-->
# New contributor declaration
- [ ] I am not making a trivial change, such as fixing a typo in a comment.
- [ ] I have written a PR description following these
[rules](https://cbea.ms/git-commit/#why-not-how).
- [ ] I have run pre-commit run --from-ref origin/main --to-ref HEAD.
- Select one of the following.
- [ ] I have added tests.
- /test for lit tests
- /unittest for C++ tests
- /python/test for end-to-end tests
- [ ] This PR does not need a test because FILL THIS IN.
- Select one of the following.
- [ ] I have not added any lit tests.
- [ ] The lit tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices),
including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)
See merge request: Ascend/triton-ascend!1665
fix(makefile): correct generalization_cases path for tests
Co-authored-by: candyhong<1102229410@qq.com>
# message auto-generated for no-merge-commit merge:
!1114 merge main/fix-makefile into main
fix(makefile): correct generalization_cases path for tests
Created-by: candyhong
Commit-by: candyhong
Merged-by: ascend-robot
Description: ## Background
The generalization_cases test directory has been relocated to third_party/ascend/unittest/generalization_cases in the main branch, but the corresponding path references in the Makefile were not updated synchronously. This inconsistency could lead to test execution failures.
---
## Changes Made
1. Align Makefile with actual directory structure
2. Optimize script comments in run_prtest.sh
---
## Checklist
- [x] I am not making a trivial change, such as fixing a typo in a comment.
- [x] I have written a PR description following these
[rules](https://cbea.ms/git-commit/#why-not-how).
- [x] I have run pre-commit run --from-ref origin/main --to-ref HEAD.
- Select one of the following.
- [ ] I have added tests.
- /test for lit tests
- /unittest for C++ tests
- /python/test for end-to-end tests
- [x] This PR does not need a test because it only fixes test directory configuration and script comments..
- Select one of the following.
- [x] I have not added any lit tests.
- [ ] The lit tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices),
including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)
See merge request: Ascend/triton-ascend!1114