That passed! So it seems the bug is limited to only gp311, when combined with uv/build[uv]. My guess is on some kind of Windows path bug with GraalPy311, does that sound plausible @timfel ? (see #2734 (comment) for the error we've been debugging, I'm curious about the use of D: vs C: drives as a possible trigger).

My inclination is to skip the test, document known issue and move on. This workaround in the tests is ugly though (global state). How long would you like to continue supporting gp311 in cibuildwheel Tim? I remember spring 26 was a possible answer. In that case I'd be happy for this workaround to live in the tests for a few months.

A test skip & mention in docs is probably fine.

sorry, I have been out sick and had not seen this.

My guess is on some kind of Windows path bug with GraalPy311, does that sound plausible @timfel ?

it does, we've found quite a few windows issues during the upgrade to 3.12

How long would you like to continue supporting gp311 in cibuildwheel Tim?

We released the latest graalpy in September, at some point we said giving people 6 months overlap should be fine, so I wouldn't mind dropping gp311 by the end of March, if that's ok with you?

I wouldn't mind dropping gp311 by the end of March, if that's ok with you?

Sounds good. We can pull out this test hackery then.

@copilot add a small mention to docs about the incompatibility of GraalPy311 with build[uv] and uv on windows.

@joerick I've opened a new pull request, #2751, to work on those changes. Once the pull request is ready, I'll request review from you.

Gah! It's now decided to fail on gp312 as well! Here's the error-

Building wheel...
\xd7 Failed to build
\u2502 C:\\Users\\runneradmin\\AppData\\Local\\Temp\\pytest-of-runneradmin\\pytest-1\\popen-gw3\\test_uv_0\\project
\u251c\u2500\u25b6 The build backend returned an error
\u2570\u2500\u25b6 Call to setuptools.build_meta:__legacy__.get_requires_for_build_wheel
failed: failed to open file
D:\\a\\_temp\\setup-uv-cache\\builds-v0\\.tmpt0SnPs\\get_requires_for_build_wheel.txt:
The system cannot find the file specified. (os error 2) (exit code: 0)
hint: This usually indicates a problem with the package or the build
environment.
::error::cibuildwheel: Command ['C:\\hostedtoolcache\\windows\\uv\\0.10.7\\x86_64\\uv.EXE', 'build', '--python=python', 'C:\\Users\\runneradmin\\AppData\\Local\\Temp\\pytest-of-runneradmin\\pytest-1\\popen-gw3\\test_uv_0\\project', '--wheel', '--out-dir=C:\\Users\\runneradmin\\AppData\\Local\\Temp\\cibw-run-jhxnk6y1\\gp312_250-win_amd64\\built_wheel'] failed with code 2. \r


Looks to be the same issue. I don't suppose you have any ideas @timfel ?

My priority is to get the CI green, so I'm gonna skip that for now. #2754 tracks the bug.