Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CMake 3.29] - Directory does not exist: C:/Windows/System32/config/systemprofile/AppData/Local/vcpkg/registries/git-trees/SHA1 #38501

Closed
bansan85 opened this issue Apr 30, 2024 · 5 comments
Assignees
Labels
category:question This issue is a question Stale

Comments

@bansan85
Copy link
Contributor

bansan85 commented Apr 30, 2024

Describe the bug
Related to #38329

I have multiple VM that run gitlab-runner. In one Windows VM, vcpkg fails since commit dd9f9d5 (Update CMake to 3.29.0 (#37457)).

I have error:

D:\CI\builds\common\sw\urx\vcpkg-registry\triplets\x64-windows-static-md-release-env.cmake: info: loaded overlay triplet from here
C:\Windows\System32\config\systemprofile\AppData\Local\vcpkg\registries\git-trees\88a7058fc7fa73a9c4c99cfcae9d79e2abf87a5a: info: installing overlay port from here
CMake Error at scripts/ports.cmake:138 (message):
  Cannot find port: vcpkg-cmake
    Directory does not exist: C:/Windows/System32/config/systemprofile/AppData/Local/vcpkg/registries/git-trees/88a7058fc7fa73a9c4c99cfcae9d79e2abf87a5a
error: building vcpkg-cmake:x64-windows-static-md-release-env failed with: BUILD_FAILED

I have the error with CMake downloaded by vcpkg or with CMake accessible from the path.

I have no idea if the problem comes from CMake or from vcpkg.

Environment

  • OS: Windows 23H2 22631.3447

Failure logs
Before CMake 3.29:
success.log

Since CMake 3.29:
failure.log

@Cheney-W Cheney-W added the category:question This issue is a question label May 6, 2024
@Cheney-W
Copy link
Contributor

Cheney-W commented May 6, 2024

The cmake in vcpkg has been update to 3.29.2, dose this issue still exist?

@bansan85
Copy link
Contributor Author

bansan85 commented May 6, 2024

@Cheney-W Yes CMake 3.29.2 fixes the issue. Strange... I was pretty sure I tested a commit after this one. I will repoen the issue if problem appears again.

@bansan85 bansan85 closed this as completed May 6, 2024
@bansan85
Copy link
Contributor Author

@Cheney-W I tried to update to master (cbf4a66) and problem appears again. I bisected (problem is reproducible) and found that 2eab0f6 is bad.

2eab0f6ee-bad.log

4af63c6-ok.log

And again, I have no idea what's wrong and set $Env:LOCALAPPDATA to a temporary directory is a good workaround.

@bansan85 bansan85 reopened this May 10, 2024
@dg0yt
Copy link
Contributor

dg0yt commented May 10, 2024

-- Running vcpkg install
Fetching registry information from https://git.moduleus.com/common/sw/3rdparty/vcpkg.git (master)...
Detecting compiler hash for triplet x64-windows-static-md-release-env...
Compiler found: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe
The following packages will be built and installed:
    catch2:x64-windows-static-md-release-env@3.5.4 -- C:\Windows\System32\config\systemprofile\AppData\Local\vcpkg\registries\git-trees\79536429a52319190e793f8ec7c19c6142b26bd4
    hdf5[core,cpp]:x64-windows-static-md-release-env@1.8.23 -- D:\CI\builds\common\sw\urx\vcpkg-registry\ports/hdf5/1.8.23
    pybind11:x64-windows-static-md-release-env@2.12.0 -- C:\Windows\System32\config\systemprofile\AppData\Local\vcpkg\registries\git-trees\fdb8e4d4c69b8a217e5cfc387ec750d4143738cc
    vcpkg-cmake:x64-windows-static-md-release-env@2024-04-18 -- C:\Windows\System32\config\systemprofile\AppData\Local\vcpkg\registries\git-trees\a10a94e8d0071ed4804d40d0f0f0c5e4e7180afd
    vcpkg-cmake-config:x64-windows-static-md-release-env@2022-02-06#1 -- C:\Windows\System32\config\systemprofile\AppData\Local\vcpkg\registries\git-trees\8d54cc4f487d51b655abec5f9c9c3f86ca83311f

You are not using only the vcpkg registry. Maybe you need to include about your registry setup.

Copy link

github-actions bot commented Jun 8, 2024

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

@github-actions github-actions bot added the Stale label Jun 8, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:question This issue is a question Stale
Projects
None yet
Development

No branches or pull requests

3 participants