Improve Windows CI - #6092
Improve Windows CI#6092ndabas wants to merge 3 commits into
Conversation
|
Quick question, didn't look closely - There's a dedicated workflow for windows-on-arm, does the added job do something different ? |
Yes, that job runs a configure/build/test with Visual Studio, only on Windows ARM64. I guess that was added as a separate workflow because Azure Pipelines does not currently support Windows ARM64. The new job does have a bit of overlap with this one, bit it also runs on Windows x64 in addition to ARM64, and runs This is why I suggested that we fold both into a single workflow, let me know if that sounds like a better idea -- I'll go ahead and do that. |
|
Of course it's up to you if you would like to keep all of these changes -- if the added workflow doesn't make sense, I can remove that commit and we can keep only the Azure pipelines fixes ( |
Following on from #6091. A few improvements for the Windows side of things:
Windows_clang_cmake,Windows_flang_clangandWindows_cl_flangjobs were silently failing (examples: 1, 2, 3) in Azure pipelines:vswhere.flangpackage did not include runtime libraries so addedflang-rt_win-64.ctest --no-tests=error..github/workflows/windows_make_install.ymlto test for OpenBLASConfig.cmake from the Makefile build on Windows has no OpenBLAS::OpenBLAS target: echo lines are missing the redirect #6084. Let me know if you would rather fold this into the existing Windows ARM64 workflow (and call thatwindows.ymlinstead.)msys2job in.github/workflows/dynamic_arch.yml.