-
Notifications
You must be signed in to change notification settings - Fork 6.8k
test_subgraph_exe1 fails on windows #19915
Comments
The first time I see a related error on master branch windows-cpu is https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fwindows-cpu/detail/master/2455/pipeline of e164cee
|
The error occurs for the network
with @samskalicky Do you think we can change the shape of |
no idea, if its flaky then its working (sometimes) and we should figure out why it fails. Just changing the inputs is not a good way to "fix" this, but might be a good place to debug if that makes the problem go away consistently. But that shouldnt be the final resolution, that just hides the problem |
This essentially blocks the master CI. I marked more subgraph tests for disabling on windows in #19908 |
So these tests pass on linux but are flaky on windows? is that the current state of things? |
Yes. Maybe there was a change to the Windows CI infrastructure that triggered this. I'm not sure. |
Are we still seeing this error? @leezu |
The test is currently disabled on Windows: If you think it has been fixed, let's re-enable it :) |
I recently set up master with an internal build/CI system, and see the reported failure on linux, but so far only on the CI machines when running the full test suite. The test_subgraph_exe* tests pass when run individually on a non-CI machine. The failure I'm seeing matches the reported one:
This error text comes from the macro SHAPE_ASSIGN_CHECK, which calls shape_assign(): My confusion is in the interpretation of the shape [1,0,2,2]. It seems the test author wanted the C-dimension of this input weight tensor shape to be inferred. However, shape_assign() seems to be applying the 'np_shape' view of the shape, where a 0 represents a known 0-size, generally reserved for a scalar (so incompatible with [1,3,2,2]. I wonder if a 'use_np_shape' mode is being non-deterministically applied somehow to this test. Thoughts anyone? |
https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fwindows-cpu/detail/PR-19908/2/pipeline
The text was updated successfully, but these errors were encountered: