-
Notifications
You must be signed in to change notification settings - Fork 7.1k
CI is toasted #6138
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
Comments
We can add a script to create a symlink from one to another, if header is not available (Or |
Doesn't appear so, pytorch/pytorch#77037 cc @dzdang |
To copy-paste a comment from #6133 : jobs that are broken depend on torchdata, which nightly build failed yesterday, so it forces torch nightly installation prior to that change. |
@malfet Sorry, just saw this. yeah, I think in retrospect, I should've marked the PR as bc-breaking. sorry about that (wasn't aware of existent projects that depended on the header file that wasn't part of the pytorch and fbcode codebase). do we need to revert the PR, or proceed with the solution above? |
Also, looks like M1 CI is somehow affected by this as well:
|
@dzdang I guess it's a question of whether we have any public facing tutorials/docs talking about AffineQuantizer, etc |
@malfet We don't. I took a look at |
Removed locally the include and can confirm that torchvision compiles and test_ops.py::test_qnms are passing. |
As @vfdev-5 proposed in #6138 (comment) Co-authored-by: vfdev <vfdev.5@gmail.com>
#6141 merged, closing. Thanks everyone. |
Summary: As vfdev-5 proposed in #6138 (comment) Reviewed By: YosuaMichael Differential Revision: D37038113 fbshipit-source-id: 3a63f0228ebac448e4ed4394c906fbd30b7f1030 Co-authored-by: vfdev <vfdev.5@gmail.com>
Uh oh!
There was an error while loading. Please reload this page.
From bf1914c on main branch:
Because torch core renamed
affine_quantizer.h
intoAffineQuantizer.h
.This will eventually be fixed by #6133. The irony is that some jobs are relying on the nightly from today while some other jobs are still relying on nightlies from yesterday where the changes from core haven't propagated. So these jobs are red on #6133.
I guess we'll have to wait till tomorrow to merge #6133 and get our green CI back.
cc @seemethere
The text was updated successfully, but these errors were encountered: