Skip to content
Open
Changes from all commits
Commits
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
3 changes: 3 additions & 0 deletions .github/workflows/ci.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -40,13 +40,15 @@ jobs:
defaults:
run:
shell: bash -l {0}
continue-on-error: ${{ matrix.allowed-failure }}
Copy link
Contributor

@ianhi ianhi Oct 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this might have some unintended consequences.

Just for this PR I'd suggest introducing a failure in the non-flaky pytest to make sure the job still fails. My memory of how this works is that if job will not turn red.

I see now. But beware that i think this means the flaky test will always be green now

strategy:
fail-fast: false
matrix:
os: ["ubuntu-latest", "macos-latest", "windows-latest"]
# Bookend python versions
python-version: ["3.11", "3.13"]
env: [""]
allowed-failure: [false]
include:
# Minimum python version:
- env: "bare-minimum"
Expand All @@ -68,6 +70,7 @@ jobs:
- env: "flaky"
python-version: "3.13"
os: ubuntu-latest
allowed-failure: true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ahh wait I was confused by this being below. this impacts the continue-on-error above?

# The mypy tests must be executed using only 1 process in order to guarantee
# predictable mypy output messages for comparison to expectations.
- env: "mypy"
Expand Down
Loading