pymc-devs/pymc

Fail tests with unexpected warnings

Open

#6,408 创建于 2022年12月21日

在 GitHub 查看
 (6 评论) (0 反应) (0 负责人)Python (7,926 star) (1,902 fork)batch import
beginner friendlyhelp wantedmaintenancetests

描述

Description

Some great maintenance work to cleanup warnings was done in #6067 and #6074 (probably more)

More recently, I started adding pytestmark = pytest.mark.filterwarnings("error"), as in #6407

Ideally, we would move to failing with warnings in the entire test suite, so that we don't regress and catch deprecation issues earlier on. The approach taken in #6407 might be a good start if there's too much going on.

https://docs.pytest.org/en/7.1.x/how-to/capture-warnings.html

贡献者指南

技术栈
python
领域
testing
议题类型
test
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
pytestPython warning filters
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
70
研究方向
Start by examining the approach taken in PR #6407, which added 'pytestmark = pytest.mark.filterwarnings("error")' to some tests. Then, consider applying the same marker globally in the test configuration, optionally using pytest's configuration files to treat all warnings as errors. Be prepared to fix any tests that currently trigger warnings, which may involve updating deprecated usage or adding expected warning filters.