-
Notifications
You must be signed in to change notification settings - Fork 615
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
test: turn PL deprecation warnings into errors #4823
Conversation
Hello. You may have forgotten to update the changelog!
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4823 +/- ##
==========================================
- Coverage 99.65% 99.64% -0.01%
==========================================
Files 381 381
Lines 34346 34086 -260
==========================================
- Hits 34226 33965 -261
- Misses 120 121 +1 ☔ View full report in Codecov by Sentry. |
So I get:
which is weird that this happens locally for me but not in the CI. Especially if you aren't seeing any problems ... 🤷 |
nice find, turns out I was seeing it locally too! I only tested a particular case locally. The error comes up during test collection, and we don't see it in CI because we specify the -p no:warnings option, which suppresses the early-loading of |
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.
I am wondering if we should instead explicitly silence the warnings that occur during collection, but I'm ok with this solution too.
confirmed locally that it works, and it won't be raised if the warning is caught/suppressed in a test