eine

FTR, https://github.com/msys2/setup-msys2/issues/145#issuecomment-874419391 was fixed in #148.

You can get the location of the MSYS2 installation by executing `cygpath -m /`. See https://github.com/msys2/setup-msys2/runs/6554920729?check_suite_focus=true#step:5:7 and https://github.com/msys2/setup-msys2/blob/main/.github/workflows/Test.yml#L399.

As commented in https://github.com/msys2/setup-msys2/pull/228#issuecomment-1135896940, I added a couple of examples to show how to save the MSYS2 root location to a variable, either from powershell or from python: https://github.com/msys2/setup-msys2/blob/066de4c88c57fc6eab4f261ae558c6a567bbe372/.github/workflows/Test.yml#L400-L408

@lazka, I guess we need to have some packages regenerated on the new setup? That is, this issue is transitory because some packages were built with the old setup but...

@jeremyd2019 maybe it's the cache of their MSYS2 job in CI the one remembering old paths?

Maybe we should support optionally specifying `msysRootDir` as an absolute path?

@lazka my point is that this did not arise before because the prefix did match (when building Python in CI and when using it in CI). As soon as Python...

@lazka, I did not check whether this is a problem with `pytest` only, or with any Python script which uses `check_call` or other resources from `subprocess`. > Not sure if...

@lazka, the use case is using pytest in MINGW32/MINGW64 to handle multiple test scripts. Some are makefiles, other are python scripts, other are shell scripts. See https://github.com/msys2/setup-msys2/commit/c167722af9b757063fd9c0e21f6aeb689e9d076a. So, it is...

This is the result if `bash` is not called: - https://github.com/msys2/setup-msys2/commit/f01e00cfeb5344c03a54b1a3d419afc7a82addcb - https://github.com/msys2/setup-msys2/runs/899776128?check_suite_focus=true