Closed Salv1a closed 2 months ago
have to add from ..utils import libentry
to test reduction ops case?
have to add
from ..utils import libentry
to test reduction ops case?
not necessary, but recommend rebasing on the latest master branch and running ci again.
have to add
from ..utils import libentry
to test reduction ops case?not necessary, but recommend rebasing on the latest master branch and running ci again.
already rebased, please approve ci
what's wrong...?
what's wrong...?
We'll take a look. Thanks.
what's wrong...?
add unit test parameter to cover the case you mentioned, and coverage check will pass.
what's wrong...?
add unit test parameter to cover the case you mentioned, and coverage check will pass.
Already modified the op test parameter, but in an inelegant way: we did not modify REDUCTION_SHAPE
to avoid potential errors. Maybe you should consider increasing REDUCTION_SHAPE
to ensure the accuracy of the tests.
PR Category
Operator
Type of Change
Bug Fix
Description
We found an issue with the definition of
cols_offsets
in theindex_select
operator. WhenN
is larger thanBLOCK_N
, the indices cannot cover all the input columns.Issue
REDUCTION_SHAPES=(4096,n)
, we forcedBLOCK_N=2048
. Whendim=0
,test_reduction_ops.py::test_accuracy_index_select
failed.REDUCTION_SHAPES=(4096*m,n)
. Whendim=0
,test_reduction_ops.py::test_accuracy_index_select
failed.Progress
Advice
We suggest to increase the input dimensions in the test cases, ensuring that the input dimensions are larger than the dimensions of the Triton sub-blocks, in order to improve test accuracy.