Joe Rickerby

The CI failures are the > WARNING: Skipping page https://pypi.org/simple/xxx/ because the GET request got Content-Type: Unknown ones. Having seen more of this recently I investigated a little https://github.com/pypa/cibuildwheel/issues/1254

Could well be possible. The Linux build calls `docker` as a subprocess to perform the build. Can Drone.io Docker runners get access to a Docker daemon somehow?

Cool - it's possible we wouldn't have to modify cibuildwheel at all to make this work - it should detect a CI environment using the `CI` env var that's set...

Hard to say without knowing - what's your idea? The main cost would be added complexity - if it's simple to implement, it could be worth it.

interesting... I note that this would change the order of execution - all would build, then all would test. But how would this be exposed to the user?

Hey Jonathan! Thanks for the issue. Have you tried appending your 'copy out' command to the end of the TEST_COMMAND? You can do something like this `CIBW_TEST_COMMAND="test_command && after_successful_test_command"`. Let...

It wouldn't be too much work to add, but maybe for now we could have better docs for this kind of use case. The coverage report is something that we...

Thank you @s-weigand - your `copy_coverage_cibuildwheel_docker ` and using the `/output` dir is a clever trick! I wonder if we could build in a post test command that supported this...

Hi @bdice ! Thanks for writing this up. We do have a reference to `ilammy/msvc-dev-cmd` in the docs, though it might be a little hard to find: https://cibuildwheel.readthedocs.io/en/stable/cpp_standards/#windows-and-python-27 Does the...

We've seen a similar feature request before - #115 discusses how we might design a feature to extract coverage reports from builds. The challenge is that the build runs so...