Actually, building from source is working on the coverage tests, but it's trying to assume pybind11 is installed and then trying to run tests from its top-level directory and for PyBaMM. We have wanted to remove the git-clone for pybind11 in pybamm-team/PyBaMM#3560 but it has been stalled for many reasons.

I have pushed d63fc76 which should fix this. I haven't added this step to the build: job – I shall do that in a moment (edit: done in 91644c5)

@BradyPlanden this should be ready for review now. Windows wheels for PyBaMM take ~20 minutes to build, and this can be reduced to ~4 minutes with caching for vcpkg triplets – this is not worth using since they are broken as previously discussed. The Linux and macOS PyBaMM wheels are being compiled in ~3 minutes and work well – all of the test failures are coming from the PyBOP suite and you may take this up to fix up the test cases, either here, or merge this PR and then continue on #176, which is where these commits shall show up and then can be merged into the develop branch when ready.

The Windows tests can be disabled by setting if: false for the step in a further commit and a temporary pytest marker

import sys
import pytest

ON_WINDOWS = sys.platform() == "win32"

@pytest.mark.skipif(ON_WINDOWS, reason="PyBaMM v24.1 is currently broken for Windows")

can be added as necessary, which should resolve everything that has to be taken care of. The Windows wheels take a long time to build, I guess pip install .[all] -vv (i.e., two levels of increased verbosity) should provide enough verbose logging.