You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The traces might show that a call is being made with a conditional scalar, but then a call is made with an array. If there is a bug in the kernel, it's hard to know which specialization is to blame given the trace.
Component(s)
C++
The text was updated successfully, but these errors were encountered:
…in the if-else kernel tests (#36825)
### Rationale for this change
The traces might show that a call is being made with a conditional scalar, but then a call is made with an array. If there is a bug in the kernel, it's hard to know which specialization is to blame given the trace.
### What changes are included in this PR?
A simplification of the `CheckWithDifferentShapes` and addition of a bit more tracing information.
### Are these changes tested?
Yes. The changes are only made to test code and I verified that bugs in the implementation get caught by the new code.
### Are there any user-facing changes?
No.
* Closes: #36824
Authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>
Signed-off-by: Antoine Pitrou <antoine@python.org>
…hapes in the if-else kernel tests (apache#36825)
### Rationale for this change
The traces might show that a call is being made with a conditional scalar, but then a call is made with an array. If there is a bug in the kernel, it's hard to know which specialization is to blame given the trace.
### What changes are included in this PR?
A simplification of the `CheckWithDifferentShapes` and addition of a bit more tracing information.
### Are these changes tested?
Yes. The changes are only made to test code and I verified that bugs in the implementation get caught by the new code.
### Are there any user-facing changes?
No.
* Closes: apache#36824
Authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>
Signed-off-by: Antoine Pitrou <antoine@python.org>
…hapes in the if-else kernel tests (apache#36825)
### Rationale for this change
The traces might show that a call is being made with a conditional scalar, but then a call is made with an array. If there is a bug in the kernel, it's hard to know which specialization is to blame given the trace.
### What changes are included in this PR?
A simplification of the `CheckWithDifferentShapes` and addition of a bit more tracing information.
### Are these changes tested?
Yes. The changes are only made to test code and I verified that bugs in the implementation get caught by the new code.
### Are there any user-facing changes?
No.
* Closes: apache#36824
Authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>
Signed-off-by: Antoine Pitrou <antoine@python.org>
Describe the enhancement requested
The traces might show that a call is being made with a conditional scalar, but then a call is made with an array. If there is a bug in the kernel, it's hard to know which specialization is to blame given the trace.
Component(s)
C++
The text was updated successfully, but these errors were encountered: