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
FAILED tests/python_frontend/augassign_wcr_test.py::test_augassign_wcr4 - assert False
+ where False = <function allclose at 0x7fe7a396e4f0>(array([1., 3., 6., 6., 5., 6., 6., 6., 5., 3.]), array([1., 3., 6., 6., 6., 6., 6., 6., 5., 3.]))
+ where <function allclose at 0x7fe7a396e4f0> = np.allclose
Here, clearly the 5th value of the left array (val coming from the DaCe generated program) should be a 6 and not a 5.
This test passed previous runs and also the following run to master. It currently seems unlikely that a bug was temporarily introduced and later fixed. It seems more likely that we have a bug which only causes test failures rarely (if a race-condition gets triggered the right way).
A possible next step would be to look at the generated source for this DaCe program and verify if the source code should properly protect against a potential race-condition.
(I'm currently working on other things, but wanted to create this issue for tracking...)
The text was updated successfully, but these errors were encountered:
There was a test failure during a normal push to master run (we run CI for every push to master which includes merging a PR):
https://github.com/spcl/dace/actions/runs/6906483658/job/18791617536#step:6:2301
The affected test runs this DaCe program:
dace/tests/python_frontend/augassign_wcr_test.py
Lines 44 to 51 in 12b9981
Which gets tested here:
dace/tests/python_frontend/augassign_wcr_test.py
Lines 158 to 163 in 12b9981
The failure is summarized by this log excerpt:
Here, clearly the 5th value of the left array (
val
coming from the DaCe generated program) should be a6
and not a5
.This test passed previous runs and also the following run to master. It currently seems unlikely that a bug was temporarily introduced and later fixed. It seems more likely that we have a bug which only causes test failures rarely (if a race-condition gets triggered the right way).
A possible next step would be to look at the generated source for this DaCe program and verify if the source code should properly protect against a potential race-condition.
(I'm currently working on other things, but wanted to create this issue for tracking...)
The text was updated successfully, but these errors were encountered: