Problems with VS2022 activation in Azure CI with version 14.37

[TonyXiang8787]

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

The MSVC version in Azure CI has been upgraded to 14.37. We get now errors when vs2022 tries to activate version 14.36 which does not exist anymore in de Azure CI image. See this build log.

**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.7.3
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************
[ERROR:vcvars.bat] Toolset directory for version '14.36' was not found.
[ERROR:VsDevCmd.bat] *** VsDevCmd.bat encountered errors. Environment may be incomplete and/or incorrect. ***
[ERROR:VsDevCmd.bat] In an uninitialized command prompt, please 'set VSCMD_DEBUG=[value]' and then re-run
[ERROR:VsDevCmd.bat] vsdevcmd.bat [args] for additional details.
[ERROR:VsDevCmd.bat] Where [value] is:
[ERROR:VsDevCmd.bat]    1 : basic debug logging
[ERROR:VsDevCmd.bat]    2 : detailed debug logging
[ERROR:VsDevCmd.bat]    3 : trace level logging. Redirection of output to a file when using this level is recommended.
[ERROR:VsDevCmd.bat] Example: set VSCMD_DEBUG=3
[ERROR:VsDevCmd.bat]          vsdevcmd.bat > vsdevcmd.trace.txt 2>&1

Similar problem has occurred in #63 and has been fixed in #64.

Installed packages

not applicable

Environment info

Windows Build in Azure CI using VS2022

[TonyXiang8787]

@h-vetinari could you please have a look? I tried to contribute a PR here, but I have no idea how to get the new sha256 and uuid field in conda_build_config.yaml.

[jaimergp]

cc @conda-forge/vc for visibility / awareness.

[isuruf]

I have no idea how to get the new sha256 and uuid field in conda_build_config.yaml.

See

vc-feedstock/recipe/conda_build_config.yaml

Lines 37 to 39 in 97ada02

	# This is the uuid in the URL; redirect can be resolved e.g. as follows
	# curl -ILSs https://aka.ms/vs/17/release/vc_redist.x64.exe | grep "Location:"
	# curl -ILSs https://aka.ms/vs/17/release/vc_redist.arm64.exe | grep "Location:"

[mjcarroll]

A note that the aka.ms link still returns the 14.36.32532 installer for me and has the same uuid in the URL.

It may be an earlier candidate on Azure before the rest of the community gets it?

[h-vetinari]

Thanks for the report. Previously, MSFT only used the "LTS" versions in the images, which happened to be the even releases for the last couple of updates.

If the images are indeed on 19.37 now, we'll have to upgrade. I guess we're not seeing this widely because it only affects vs2022, which your feedstock is using, but not the default in conda-forge. Unless you're using very recent C++ features, you should also be fine with downgrading that to vs2019?

If not, could you open a PR along the lines of adab9a3 & f54ce13?

[TonyXiang8787]

A note that the aka.ms link still returns the 14.36.32532 installer for me and has the same uuid in the URL.

It may be an earlier candidate on Azure before the rest of the community gets it?

Hi @mjcarroll, in the Azure image (and also in my local laptop) is the version of MSVC runtime still at 14.36.32532. The cl compiler version has been upgraded to 19.37.32822 and the toolchain version is 14.37.32822, which is needed in the command call of vcvars64.bat -vcvars_ver=.

Thanks for the report. Previously, MSFT only used the "LTS" versions in the images, which happened to be the even releases for the last couple of updates.

If the images are indeed on 19.37 now, we'll have to upgrade. I guess we're not seeing this widely because it only affects vs2022, which your feedstock is using, but not the default in conda-forge. Unless you're using very recent C++ features, you should also be fine with downgrading that to vs2019?

If not, could you open a PR along the lines of adab9a3 & f54ce13?

Hi @h-vetinari, indeed we use the latest C++ features. Therefore we need vs2022 in the pipeline. I will make a PR.