This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients JelleZijlstra, christian.heimes, pitrou, rhettinger, vstinner, xtreak
Date 2021-04-12.12:30:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1618230647.21.0.72176411995.issue43723@roundup.psfhosted.org>
In-reply-to
Content
> Tests should treat any unhandled deprecation warnings as a test failure.

libregrtest sets a sys.unraisablehook: a test is marked as "failed" if any "unraisable exception" is logged.

libregrtest might use a hook on warnings to do the same: log the warning, but mark the test as failed?

One issue that I had with libregrtest and sys.unraisablehook was that some "unraisable exception" was not logged in buildbot logs. I had to use sys.__stderr__ to ensure that the exception is logged. See regrtest_unraisable_hook() of test.libregrtest.utils.

It would be annoying to get a test marked as "FAILED" if the warning is not visible in logs :-(

---

Using -Werror on some CIs would be another option.
History
Date User Action Args
2021-04-12 12:30:47vstinnersetrecipients: + vstinner, rhettinger, pitrou, christian.heimes, JelleZijlstra, xtreak
2021-04-12 12:30:47vstinnersetmessageid: <1618230647.21.0.72176411995.issue43723@roundup.psfhosted.org>
2021-04-12 12:30:47vstinnerlinkissue43723 messages
2021-04-12 12:30:47vstinnercreate