Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[MAINTENANCE] Formatting, lint ignores .git-blame-ignore-revs #9578

Merged
merged 4 commits into from
Mar 6, 2024
Merged

[MAINTENANCE] Formatting, lint ignores .git-blame-ignore-revs #9578

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7cfa6d3
add `.git-blame-ignore-revs`
Kilo59 Mar 5, 2024
7218096
don't error for `PendingDeprecation`
Kilo59 Mar 6, 2024
62f4d7b
"fix" failing PACT test
Kilo59 Mar 6, 2024
2016db7
Merge branch 'develop' into m/_/ignore-revs
Kilo59 Mar 6, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
don't error for PendingDeprecation
  • Loading branch information
@Kilo59
Kilo59 committed Mar 6, 2024
commit 72180967c14a659bfd5b38c25e7388a93e795a91
5 changes: 5 additions & 0 deletions pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -360,9 +360,14 @@ If you are working in a configuration file you may use the inline comment \
# -----------------------------------------------------------------

[tool.pytest.ini_options]
# https://docs.python.org/3/library/warnings.html#the-warnings-filter
filterwarnings = [
# Turn all warnings not explicitly filtered below into errors
"error",
# PendingDeprecationWarning: these relate to the use of methods that are not even deprecated yet.
# We want to see the warnings in the logs, but not have them cause CI to fail.
"once::PendingDeprecationWarning",

# This warning is common during testing where we intentionally use a COMPLETE format even in cases that would
# be potentially overly resource intensive in standard operation
"ignore:Setting result format to COMPLETE for a SqlAlchemyDataset:UserWarning",
Expand Down
Loading