Description
Could cibuildwheel define a new placeholder {python-version} set to things like 3.14, for use in CIBW_TEST_COMMAND?
This would allow gathering of pytest results with pytest --junit-xml=test-results{pythonversion}-xml when cibuildwheel builds and tests for a range of Python versions.
At the moment with something like CIBW_BUILD='cp310* cp311* cp312* cp313* cp314*' and CIBW_TEST_COMMAND='pytest --junit-xml=test-results.xml', the invocation of pytest for each python version overwrites the existing test-results.xml file, so we can't gather complete information.
It might be useful to have more information than just the python version. In which case how about:
- A
{wheel-leafname} placeholder that identifies the exact wheel that was tested.
- A
{system} placeholder containing a wheel name-style <python-tag>-<abi-tag>-<platform-tag> string to identify the environment in which tests were run?
Build log
No response
CI config
No response
Description
Could cibuildwheel define a new placeholder
{python-version}set to things like3.14, for use in CIBW_TEST_COMMAND?This would allow gathering of pytest results with
pytest --junit-xml=test-results{pythonversion}-xmlwhen cibuildwheel builds and tests for a range of Python versions.At the moment with something like
CIBW_BUILD='cp310* cp311* cp312* cp313* cp314*'andCIBW_TEST_COMMAND='pytest --junit-xml=test-results.xml', the invocation of pytest for each python version overwrites the existingtest-results.xmlfile, so we can't gather complete information.It might be useful to have more information than just the python version. In which case how about:
{wheel-leafname}placeholder that identifies the exact wheel that was tested.{system}placeholder containing a wheel name-style<python-tag>-<abi-tag>-<platform-tag>string to identify the environment in which tests were run?Build log
No response
CI config
No response