文件最后提交记录最后更新时间
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!16441 个月前
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!16441 个月前
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!16441 个月前
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!16441 个月前
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!16441 个月前