Open mbarbero opened 3 years ago
@mbarbero also reports that the C:\Program Files (x86)\Microsoft Visual Studio\2019
and C:\Program Files (x86)\Microsoft Visual Studio 12.0
directories aren't even present so this is definitely an installation error.
Possible dup of https://github.com/adoptium/infrastructure/issues/2178
@smlambert I don't believe the compilers necessarily have to match the ones used for buiding the JDK for the purposes of executing tests so this likely isn't a blocker since VS2017 installs ok. Would you agree?
We do not necessarily need to match the ones used for building JDK, but we do definitely need to verify that compiling the test natives works (there are native tests in openjdk/jck/system groups that we should verify compile without error).
I'm not seeing the VS2019 failure on the playbook checker that I've just created https://github.com/adoptium/infrastructure/pull/2232. I can confirm that the VS2013 error is happening for me though
Both installations fail while registering DIA SDK shared libraries. Note that MSVS_2019 was started only when skipping tag
MSVS_2013
.MSVS_2017 installs successfully
Any hint?