Occasional failure in win32 complex matmul
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 32.8k
- Forks
- 12.8k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 197
Description
Just a heads up that there is a flaky win32 test from the last post-merge CI run:
___________________ TestMatmul.test_vector_matrix_values _____________________
self = <numpy.core.tests.test_multiarray.TestMatmul object at 0x16138CB8>
mat1 = np.array([[1, 2], [3, 4]])
mat2 = np.stack([mat1]*2, axis=0)
tgt1 = np.array([7, 10])
tgt2 = np.stack([tgt1]*2, axis=0)
for dt in self.types[1:]:
v = vec.astype(dt)
m1 = mat1.astype(dt)
m2 = mat2.astype(dt)
> res = self.matmul(v, m1)
E RuntimeWarning: invalid value encountered in matmul
dt = 'F'
m1 = array([[1.+0.j, 2.+0.j],
[3.+0.j, 4.+0.j]], dtype=complex64)
m2 = array([[[1.+0.j, 2.+0.j],
[3.+0.j, 4.+0.j]],
[[1.+0.j, 2.+0.j],
[3.+0.j, 4.+0.j]]], dtype=complex64)
mat1 = array([[1, 2],
[3, 4]])
mat2 = array([[[1, 2],
[3, 4]],
[[1, 2],
[3, 4]]])
res = array([[ 7., 10.],
[ 7., 10.]], dtype=float64)
Contributor guide
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
Start with the Azure CI log and the TestMatmul.test_vector_matrix_values failure shown in the issue, focusing on the complex64 case and its RuntimeWarning. Reproduce the win32 failure and determine whether the test or matmul behavior needs correction; done means the intermittent warning is understood and the relevant test passes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100