Skip to content

Conversation

@h-vetinari
Copy link
Member

It seems the images with VS 17.14 are starting to be rolled out, and many windows jobs failing because of it

(%BUILD_PREFIX%) C:\Program Files\Microsoft Visual Studio\2022\Enterprise>if "14.44" LSS "14.43" (
 
 CALL "VC\Auxiliary\Build\vcvars64.bat" -vcvars_ver=14.44 10.0.26100.0 
)  else (CALL "VC\Auxiliary\Build\vcvars64.bat" -vcvars_ver=14.43 10.0.26100.0 ) 
**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.14.5
** Copyright (c) 2025 Microsoft Corporation
**********************************************************************
[ERROR:vcvars.bat] Toolset directory for version '14.43' 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

Closes #98

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Jun 19, 2025

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/15766372540. Examine the logs at this URL for more detail.

@h-vetinari
Copy link
Member Author

h-vetinari commented Jun 19, 2025

@conda-forge/vc, VS 17.14 has started rolling out in the runner-images. Please review at your earliest convenience.

I raised #98 almost a month ago, but my hopes of getting #95 in first did not pan out (otherwise I would have raised this PR right after), so now I'm opening it as a minimal change to fast-track things. If breakage becomes severe enough (given that we're now defaulting to VS2022), I will merge, considering the blast radius.

@isuruf isuruf merged commit d33641b into conda-forge:main Jun 19, 2025
13 checks passed
@isuruf
Copy link
Member

isuruf commented Jun 19, 2025

Hmm, this is a good reason to not go to the latest VS year. This is something to consider next time we update the VS major year

@h-vetinari h-vetinari deleted the 14 branch June 19, 2025 22:25
@h-vetinari
Copy link
Member Author

This is something to consider next time we update the VS major year

Yeah, I agree. I did think about it already this time, but considered it non-critical because 17.14 is the last minor of the 17.x series.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

VS 17.14 released

3 participants