-
Notifications
You must be signed in to change notification settings - Fork 7.2k
replace remaining asserts #5636
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
Conversation
💊 CI failures summary and remediationsAs of commit 5eac9b8 (more details on the Dr. CI page):
🕵️ 6 new failures recognized by patternsThe following CI failures do not appear to be due to upstream breakages:
|
Job | Step | Action |
---|---|---|
Run tests | 🔁 rerun |
🚧 3 ongoing upstream failures:
These were probably caused by upstream breakages that are not fixed yet.
- binary_linux_conda_py3.10_cu115 since Mar 21 (fbc8ea4)
- binary_linux_conda_py3.8_cu115 since Mar 21 (fbc8ea4)
- binary_linux_conda_py3.7_cu115 since Mar 21 (fbc8ea4)
This comment was automatically generated by Dr. CI (expand for details).
Please report bugs/suggestions to the (internal) Dr. CI Users group.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jdsgomes
tests are failing because of this change: https://github.com/pytorch/vision/pull/5636/files#diff-678e419692ae76586d9f58ce62d2841be82d607637b7d507ead76eca412fcdd1R244 I am thinking to revert and leave this particular |
Sorry, I thought I had replied to this comment but it looks like I didn't 🤦♂️ I don't know if there is a good workaround for this. But I'm surprised that we did not encouter the same error for the changes we did in #5587. Do you know why that might be the case? |
I had a very quick look on #5587 and I think it works because all of our Exceptions are either on utils/methods that are not part of the models or on model constructors. I agree with jdgomes that we should probably close the PR and leave the assertions as is. |
Abandoning this PR and will follow up with another PR reverting some of the recent exceptions added after the offline discussion with @datumbox |
Replace torch._asserts as a follow up to this PR #5587
Thanks @datumbox for raising it in #5494