-
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
[CI] [TEST] test_conv2d_int8_intrinsics #5455
Comments
cc @anijain2305 |
The error has things to do with constant int bound rebound to a different result. |
also cc @yongfeng-nv @hzfan since both of you have touched/reviewed the const int bound recently |
I also saw this error when running |
Ran the test in tvmai/ci-cpu:v0.62-t0, but couldn't reproduce the failure. |
I was able to reproduce the failure. I have not been able to solve it yet. The only pointer that I have till now is that if I disable tensorize (this test uses tensorize to use Intel VNNI), the test progresses. I am not familiar with const int bound. I will try to get familiar with it and see how tensorize impacts const int bounds.
|
Dug little bit deeper, but still not able to root cause. I think the const int bounds are good. The problem here is that two different PrimExpr have same PrimExprNode* at L150
And therefore, Expr(63) whose ConstIntBound is set correctly to [63, 63] is used to compare the bounds for Expr(15), causing failure. Will pursue this direction, please let me know of any suggestions @tqchen |
@tqchen I verified locally. This is resolved now. You can close this. |
In the past week I attempted to upgrade the docker image CPU to bionic(ubuntu 18.04), during the time, a new unittest error occurs(note that the master CI was fine) in the int8 intrinsic test,
it would be great it we can look into it. To reproduce, use the docker image
tvmai/ci-cpu:v0.62-t0
http://ci.tvm.ai:8080/job/temp-ci-docker-staging/job/ci-stage/30/execution/node/131/log/
The text was updated successfully, but these errors were encountered: