Uh oh!
There was an error while loading. Please reload this page.
Bring CI back to all-working condition - #5822
Conversation
…2@v2 cannot be run twice anymore): https://github.com/pybind/pybind11/actions/runs/17394902023/job/49417376616?pr=5796 ``` Run msys2/setup-msys2@v2 with: msystem: mingw64 install: mingw-w64-x86_64-python-numpy mingw-w64-x86_64-python-scipy mingw-w64-x86_64-eigen3 path-type: minimal update: false pacboy: false release: true location: RUNNER_TEMP platform-check-severity: fatal cache: true env: PYTHONDEVMODE: 1 PIP_BREAK_SYSTEM_PACKAGES: 1 PIP_ONLY_BINARY: numpy FORCE_COLOR: 3 PYTEST_TIMEOUT: 300 VERBOSE: 1 CMAKE_COLOR_DIAGNOSTICS: 1 MSYSTEM: MINGW64 Error: Trying to install MSYS2 to D:\a\_temp\msys64 but that already exists, cannot continue. ```
rwgk
commented
Sep 2, 2025
Hi @henryiii, could you please review? This should stop the frequent CI / 🐍 (macos-13, 3.13t, -DCMAKE_CXX_STANDARD=11) / 🧪 (pull_request) failures. |
| if env.WIN and env.PYPY: | ||
| pytest.xfail("[TEST-GIL-SCOPED] Windows PyPy: " + msg) | ||
| elif env.MACOS and not env.sys_is_gil_enabled(): | ||
| pytest.xfail("[TEST-GIL-SCOPED] macOS free-threading: " + msg) |
There was a problem hiding this comment.
This doesn't always fail, does it? So strict=False?
There was a problem hiding this comment.
The strict flag only applies to @pytest.mark.xfail(...) (the decorator/mark form). Inline pytest.xfail() doesn't take strict at all — it immediately aborts the test and reports XFAIL. There’s no concept of XPASS in this case, so strict isn't relevant here.
To be sure I looked it up the good-old way:
https://docs.pytest.org/en/stable/how-to/skipping.html#xfail-mark-test-functions-as-expected-to-fail
Note that no other code is executed after the pytest.xfail() call, differently from the marker.
| if env.PYPY and env.WIN: | ||
| pytest.skip(msg) | ||
| if env.WIN and env.PYPY: | ||
| pytest.xfail("[TEST-GIL-SCOPED] Windows PyPy: " + msg) |
There was a problem hiding this comment.
This didn't run before, now it will. Guessing that's fine?
There was a problem hiding this comment.
See other comment: Note that no other code is executed after the pytest.xfail() call, differently from the marker.
| install_mingw64_only: "" | ||
| - sys: mingw64 | ||
| env: x86_64 | ||
| install_mingw64_only: | |
There was a problem hiding this comment.
I'd name this "extra_install", I think, since it's there to install extra stuff. And you can leave it off on the other job, variables default to empty.
rwgk
commented
Sep 2, 2025
Thanks @henryiii! WDYT about disabling the two failing CIBW tests in this PR, too, until someone gets a chance to fix those? CIBW / iOS wheel macos-13 (pull_request) CIBW / iOS wheel macos-14 (pull_request) |
Ugh... It is not working as intended: @henryiii I'm a bit lost, should I maybe checking for IIUC, it's failing even though the GIL is enabled? This has been happening with macOS ever since I added this test, but only fairly infrequently. |
rwgk
commented
Sep 3, 2025
For easy future reference, the errors after commit bd3900e were: CIBW / iOS wheel macos-13 (pull_request) Failing after 1m CIBW / iOS wheel macos-14 (pull_request) Failing after 35s macos-13: macos-14: very similar |
This reverts commit bd3900e. See also: pybind#5822 (comment)
This is flaking the second time (this PR): CI / macos-13 • brew install llvm (pull_request) Failing after 10m (start time: Wed, 03 Sep 2025 06:38:28 GMT) I'll try a rerun. For completeness, the first flake was: https://github.com/pybind/pybind11/actions/runs/17422859619/job/49464452403 (start time: Wed, 03 Sep 2025 04:21:04 GMT) There was one success between the 1st and 2nd failure (https://github.com/pybind/pybind11/actions/runs/17423607165/job/49466476407, start time: Wed, 03 Sep 2025 05:07:40 GMT). Edit: 3rd failure now: https://github.com/pybind/pybind11/actions/runs/17425182772/job/49473499749?pr=5822 Edit: I added that job with PR #4326 — initially to inform PR #4319, but then I decided to keep it, to be proactive about testing clang development versions. I'm not sure we still have the manpower to be proactive in this way. Edit: 4th failure now: CI / macos-13 • brew install llvm (pull_request) |
…uce our maintenance overhead: Failures tracked here: pybind#5822 (comment)
Replaced brew upgrade with brew install for cmake.
Uninstall cmake before installing the latest version due to GitHub's local tap changes.
Uh oh!
There was an error while loading. Please reload this page.
henryiii
commented
Sep 3, 2025
GitHub is unpinning |
rwgk
commented
Sep 3, 2025
Thanks @henryiii, awesome that you could get the CIBW jobs working again with a one-line change! I'll mark my calendar to harvest the |
Description
Fix "🐍 3 • windows-latest • mingw64" CI job
Apparently
msys2/setup-msys2@v2cannot be run twice anymore:test_gil_scoped.py
xfailmacOS free-threading relatedDisable
build-iosjob in tests-cibw.yml (commit 0f5a29d)Remove
macos_brew_install_llvmjob because it started failing, to reduce our maintenance overhead:Failures are tracked here: Bring CI back to all-working condition #5822 (comment)
Suggested changelog entry: