[WIP] CI: Debug MSVC Segfault in PyTest

[ax3l]

Issue in error handler of https://github.com/ECP-WarpX/impactx/blob/48654c00f1771f1737aaa6931c43da38b80e7753/tests/python/test_impactx.py#L166 on Windows

Initializing AMReX (24.07-16-gdcb9cc0383dc)...
AMReX (24.07-16-gdcb9cc0383dc) initialized

Grids Summary:
  Level 0   1 grids  512 cells  100 % of domain

Windows fatal exception: access violation

Current thread 0x000019bc (most recent call first):
  File "D:\a\impactx\impactx\tests\python\test_impactx.py", line 166 in test_impactx_noparticles
  File "C:\hostedtoolcache\windows\Python\3.12.4\x64\Lib\site-packages\_pytest\python.py", line 159 in pytest_pyfunc_call
  File "C:\hostedtoolcache\windows\Python\3.12.4\x64\Lib\site-packages\pluggy\_callers.py", line 103 in _multicall

Likely a CI runner or pytest or CPython issue...

Debugger: cdb.exe

• https://github.com/actions/runner-images/issues/942
• https://github.com/AMReX-Codes/pyamrex/pull/91

[ax3l]

Very tricky. When running only test_impactx.py it passes. On Linux, valgrind shows no related issues... (PyRendererAgg_draw_path in MPL certainly has some uninit values...)

[ax3l]

This stopped failing with the latest Windows runner image update.

Probably an environment issue after all.