Skip to content

Commit

Permalink
ci: Don't test warnings on release tests
Browse files Browse the repository at this point in the history
* Override error on filterwarnings to avoid failing on warnings.
* Set the fail-fast to False in the CI strategy to allow for identifying
  if things are OS specific.
  • Loading branch information
matthewfeickert committed May 29, 2024
1 parent a1d8476 commit 6af7ee9
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions .github/workflows/release_tests.yml
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,7 @@ jobs:
# Intel runner
- os: macos-13
python-version: '3.12'
fail-fast: false

steps:
- uses: actions/checkout@v4
Expand All @@ -47,6 +48,10 @@ jobs:
- name: Canary test public API
run: |
# Override the ini option for filterwarnings with an empty list to disable error on filterwarnings
# as testing the latest release API still works, not the release is warning free.
# Though still show warnings by setting warning control to 'default'.
export PYTHONWARNINGS='default'
pytest tests/test_public_api.py
# FIXME: c.f. https://github.com/proycon/codemetapy/issues/24
Expand Down

0 comments on commit 6af7ee9

Please sign in to comment.