-
-
Notifications
You must be signed in to change notification settings - Fork 632
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
add PYTHONWARNINGS=ignore::DeprecationWarning to integration tests #8541
add PYTHONWARNINGS=ignore::DeprecationWarning to integration tests #8541
Conversation
This will unbreak master, but won't fix the issue that these warnings will render for users. Is it possible to fix them instead? |
I recommend reverting the deprecation of |
The larger issue would seem to me to be that seeing any deprecation warnings at all will cause our CI to break. Do we want to consider looking into fixing that before focusing on finishing up a migration process? |
I agree that most of the deprecation warning will break CI and that's bad, but I wonder how they got past CI in the first place. The solutions seems to be to: I would really love us to go with option 1, but I don't know how feasible it is. In the interest of unblocking merging, I think either reverting or fixing Also, these deprecation warnings are for pants developers, right? Would it make sense to only output them in debug mode, or in when running pants from source? |
@Eric-Arellano I am working on a fix for Collection.of today if that makes any difference here, not sure on timing exactly but hopefully by EOD. |
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.
If this looks green, then fine with landing it.
I'll follow up with a thread to discuss deprecations and removing internal usages.
Restated the failing shards (after checking they were known flakes) |
It looks like this breaks a different integration test:
|
Fixed the above. |
#8540 landed to give us some breathing room on this. @cosmicexplorer : My suggestion would be that we re-land #8509 and #8181 along with the remaining deprecation removals that @hrfuller has mentioned, because whether or not they are silenced in CI, they are triggering for our end users. |
Closing this as @Eric-Arellano has since removed |
Problem
Fixes #8539.
Solution
Result
master is unbroken!