vcpkg failing on macOS
See original GitHub issuerun-vcpkg is failing to run here, even on a rebuild, with this log:
2021-01-14T13:24:18.2723360Z ##[group]Run lukka/run-vcpkg@v5
2021-01-14T13:24:18.2723870Z with:
2021-01-14T13:24:18.2724710Z vcpkgArguments: @/Users/runner/work/Mudlet/Mudlet/3rdparty/our-vcpkg-dependencies/vcpkg-x64-osx-dependencies
2021-01-14T13:24:18.2725760Z vcpkgDirectory: /Users/runner/work/Mudlet/Mudlet/3rdparty/vcpkg
2021-01-14T13:24:18.2726930Z appendedCacheKey: ba279cb15eb6507b8ab8da50737cc246a49faf17e6d8f0bee7202d39655e603d-key
2021-01-14T13:24:18.2727980Z setupOnly: false
2021-01-14T13:24:18.2728840Z vcpkgArtifactIgnoreEntries: !.git
**/*
!installed
!/vcpkg
!vcpkg.exe
!vcpkgArtifactIgnoreEntries
2021-01-14T13:24:18.2729920Z vcpkgGitURL: https://github.com/microsoft/vcpkg.git
2021-01-14T13:24:18.2730570Z cleanAfterBuild: true
2021-01-14T13:24:18.2731050Z doNotUpdateVcpkg: false
2021-01-14T13:24:18.2731510Z useShell: true
2021-01-14T13:24:18.2731910Z doNotCache: false
2021-01-14T13:24:18.2732300Z env:
2021-01-14T13:24:18.2732980Z pythonLocation: /Users/runner/hostedtoolcache/Python/3.9.1/x64
2021-01-14T13:24:18.2733640Z Qt5_Dir: /Users/runner/work/Mudlet/Qt/5.14.1/clang_64
2021-01-14T13:24:18.2734190Z Qt5_DIR: /Users/runner/work/Mudlet/Qt/5.14.1/clang_64
2021-01-14T13:24:18.2734780Z QT_PLUGIN_PATH: /Users/runner/work/Mudlet/Qt/5.14.1/clang_64/plugins
2021-01-14T13:24:18.2735440Z QML2_IMPORT_PATH: /Users/runner/work/Mudlet/Qt/5.14.1/clang_64/qml
2021-01-14T13:24:18.2736440Z vcpkgResponseFile: /Users/runner/work/Mudlet/Mudlet/3rdparty/our-vcpkg-dependencies/vcpkg-x64-osx-dependencies
2021-01-14T13:24:18.2737440Z ##[endgroup]
2021-01-14T13:24:18.3765820Z ##[group]Restore vcpkg and its artifacts from cache
2021-01-14T13:24:18.3798640Z vcpkg identified at commitId='4b222f8d2653603b74fa5086cf0b02a1963d3911', adding it to the cache's key.
2021-01-14T13:24:18.3803160Z Cache's key = 'submodGitId=4b222f8d2653603b74fa5086cf0b02a1963d3911-args=262756201-os=-931134771-appendedKey=-1200961648'.
2021-01-14T13:24:18.3806610Z Running restore-cache
2021-01-14T13:24:20.7037240Z Cache Size: ~92 MB (96609131 B)
2021-01-14T13:24:20.7127170Z [command]/usr/bin/tar --use-compress-program zstd -d -xf /Users/runner/work/_temp/7417f9e6-5240-4776-a5ec-8b823a6cc05e/cache.tzst -P -C /Users/runner/work/Mudlet/Mudlet
2021-01-14T13:24:30.5644180Z Cache hit, id=submodGitId=4b222f8d2653603b74fa5086cf0b02a1963d3911-args=262756201-os=-931134771-appendedKey=-1200961648.
2021-01-14T13:24:30.5645890Z ##[endgroup]
2021-01-14T13:24:30.5647210Z ⏱ elapsed: 12.188 seconds
2021-01-14T13:24:30.5704840Z ##[group]Set output env vars
2021-01-14T13:24:30.5715410Z Set task output variable 'RUNVCPKG_VCPKG_ROOT_OUT' to value: /Users/runner/work/Mudlet/Mudlet/3rdparty/vcpkg
2021-01-14T13:24:30.5718940Z ##[endgroup]
2021-01-14T13:24:30.5720240Z ⏱ elapsed: 0.002 seconds
2021-01-14T13:24:30.5721860Z tool: /usr/local/bin/git
2021-01-14T13:24:30.5723190Z Fetching the commit id at /Users/runner/work/Mudlet/Mudlet/3rdparty/vcpkg
2021-01-14T13:24:30.5857980Z 4b222f8d2653603b74fa5086cf0b02a1963d3911
2021-01-14T13:24:30.5867780Z ##[group]Check whether vcpkg repository is up to date
2021-01-14T13:24:30.5870010Z Checking whether vcpkg's repository is updated to commit id '4b222f8d2653603b74fa5086cf0b02a1963d3911' ...
2021-01-14T13:24:30.5891400Z tool: /usr/local/bin/git
2021-01-14T13:24:30.8191270Z 4b222f8d2653603b74fa5086cf0b02a1963d3911 3rdparty/vcpkg (2020.04-1517-g4b222f8d2)
2021-01-14T13:24:30.8416810Z 'vcpkg' is detected as a submodule, adding '.git' to the ignored entries in '.artifactignore' file (for excluding it from caching).
2021-01-14T13:24:30.8519980Z File '.artifactsignore' content: ''**/*', '!installed', '!/vcpkg', '!vcpkg.exe', '!vcpkgArtifactIgnoreEntries', '.git''
2021-01-14T13:24:30.8551750Z Is vcpkg repository updated? Yes
2021-01-14T13:24:30.8567430Z ##[endgroup]
2021-01-14T13:24:30.8579560Z ⏱ elapsed: 0.205 seconds
2021-01-14T13:24:30.8609520Z ##[group]Check whether last vcpkg's build is up to date with sources
2021-01-14T13:24:30.8642900Z Checking last vcpkg build commit id in file '/Users/runner/work/Mudlet/Mudlet/3rdparty/vcpkg/vcpkgLastBuiltCommitId' ...
2021-01-14T13:24:30.9128400Z vcpkg executable is up to date with sources.
2021-01-14T13:24:30.9230150Z ##[endgroup]
2021-01-14T13:24:30.9332730Z ⏱ elapsed: 0.002 seconds
2021-01-14T13:24:30.9434900Z ##[group]Check vcpkg executable exists
2021-01-14T13:24:30.9482030Z vcpkg executable exists at: '/Users/runner/work/Mudlet/Mudlet/3rdparty/vcpkg/vcpkg'.
2021-01-14T13:24:30.9483290Z ##[endgroup]
2021-01-14T13:24:30.9484600Z ⏱ elapsed: 0.052 seconds
2021-01-14T13:24:30.9485620Z ##[group]Install/Update ports
2021-01-14T13:24:30.9488620Z Running 'vcpkg remove --outdated --recurse --overlay-ports=../our-vcpkg-dependencies/lua' in directory '/Users/runner/work/Mudlet/Mudlet/3rdparty/vcpkg' ...
2021-01-14T13:24:30.9560620Z dyld: Symbol not found: ___emutls_v._ZSt11__once_call
2021-01-14T13:24:30.9565730Z Referenced from: /Users/runner/work/Mudlet/Mudlet/3rdparty/vcpkg/vcpkg
2021-01-14T13:24:30.9568950Z Expected in: /usr/local/opt/gcc/lib/gcc/10/libstdc++.6.dylib
2021-01-14T13:24:30.9571640Z in /Users/runner/work/Mudlet/Mudlet/3rdparty/vcpkg/vcpkg
2021-01-14T13:24:30.9585570Z ##[error]Last command execution failed with error code 'null'.
2021-01-14T13:24:30.9601160Z ##[endgroup]
2021-01-14T13:24:30.9605260Z ⏱ elapsed: 0.090 seconds
2021-01-14T13:24:30.9606720Z Error: Last command execution failed with error code 'null'.
The PR does not touch any vcpkg-related code. Could the issue be that the Github environment has changed?
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
[vcpkg] Build failure on MacOS · Issue #15442 - GitHub
Host Environment. OS: [Mojave 10.14.6.] Compiler: revision. To Reproduce Steps to reproduce the behavior: ./bootstrap-vcpkg.sh. Failure logs
Read more >Importing C++ library installed using vcpkg on mac?
The error suggests that the C++ compiler is not aware of the location where the library was installed. How can I correctly install...
Read more >gstreamer-full causes a build failure on macOS with Apple Clang
Hi guys, I'm vcpkg maintainer. Today I'm trying to recover the gstreamer build on OSX (https://github.com/microsoft/vcpkg/pull/20814), ...
Read more >AWS SDK for C++ Setup using vcpkg on Linux/macOS
The SDK might fail to build on Amazon EC2 instance types t2.micro, t2.small, and other small instance types due to insufficient memory. To...
Read more >CMake, vcpkg, and universal builds | Apple Developer Forums
... at this time, Windows and macOS). As a result, the people who started 8 hours before I did picked CMake and vcpkg...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Posting here below the link where I asked how to fetch the required data to append to the key in order to tie the cache to a given environment version. Probably the environment and the version would be good candidates (e.g
Environment: macos-10.15
Version: 20201212.1
), as I expect them to change on updates.https://github.community/t/fetching-runner-and-environment-data-while-an-action-is-executing/155663
@vadi2 I took a quick look, but i think it is a good lead: the cache has been created in the past with a different version of the macOS GitHub environments, and the vcpkg executable is failing its execution on some missing binary dependency, i.e. dyld:
Symbol not found: ___emutls_v._ZSt11__once_call
.The environment look brand new released on 10th Jan 2021.
The solution is to change the key, so that the old cache is not used anymore, and vcpkg’s executable is being rebuilt.
I think the action should include by default the version of the image, but I am not aware of any way to fetch it. We can keep this ticket open until i found a good solution to this problem.