We used to mark all warnings as errors for our pytest runner with the intention that it'll surface deprecation warnings (so that we can fix them as soon as possible). However, with the changes in the project, it becomes difficult for us to keep up with addressing the deprecation warnings, and our CI often fails because of this.
Changes proposed
Remove the setting to turn warnings as errors so that we can leave them there until people have time to address them.
Test Plan
Please provide clear instructions on how the changes were verified. Attach screenshots if applicable.
Motivation
We used to mark all warnings as errors for our pytest runner with the intention that it'll surface deprecation warnings (so that we can fix them as soon as possible). However, with the changes in the project, it becomes difficult for us to keep up with addressing the deprecation warnings, and our CI often fails because of this.
Changes proposed
Remove the setting to turn warnings as errors so that we can leave them there until people have time to address them.
Test Plan
Please provide clear instructions on how the changes were verified. Attach screenshots if applicable.
Types of changes
Checklist