-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FLAKY] relay/test_op_level1.py::test_binary_op failing intermittently #6417
Comments
My guess the problem was due to floordivide/floormod, where there is a boundary case. So increasing tol may not help. We need to explicitly change the generator to avoid such boundary cases. There are some existing topi cases that already do this. |
@leandron would you be interested in sending a fix? |
@tqchen Yes, I’ll have a look |
There are know fixes please take a look at the issues linked |
Just to follow up here. I investigated how a fix would look like and it seems there is some manual filtering to be done on values around 0.5 for I'll to submit a PR with this filter (soon), similar to #4382, plus improve diagnostic on that test case, so in case it fails, it will give us which function (out of 6 tested on that test) is the offending one. |
ping @leandron :) |
Sorry I didn't manage to get into this yet. |
Hi folks, is this still active? |
As part of #6302, it seems there is another flaky test, that is not related to the contents of the being submitted there:
tests/python/relay/test_op_level1.py::test_binary_op
.You can see this on Jenkins for the full stack trace: https://ci.tvm.ai/blue/organizations/jenkins/tvm/detail/PR-6302/14/pipeline/185
The error message I see is:
I believe we will need to increase the tolerance, but I don't know by how much it would be adequate, so I'll just report it here.
cc @tqchen @merrymercy
The text was updated successfully, but these errors were encountered: