-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
vcpkg freeze after sucessfully building ffmpeg #5476
Comments
I'm also hitting this. I've been trying to track it down for a couple days now. It happens with both upstream, and my own trimmed down ffmpeg port. Once I've isolated the change I'll report more. You can sorta follow my (very messy) diagnosis so far at: CorsixTH/CorsixTH#1515 |
Weirdly, even though the problem only happens when building ffmpeg, it still happens when reverting the ffmpeg port to a known good version (while keeping the rest of vcpkg on the latest version). This (combined with the behaviour of just freezing) makes the issue rather hard to diagnose. |
Thank you for this! I already gave up since this is beyond my knowledge. Also, for your information, if this is helpful, my Appveyor CI build will always freeze, but not my Azure Pipelines, so I stopped using Appveyor temporarily. You can check my Azure Pipelines log here. |
Some ideas - let me know and I'll delete this comment if I'm way off the mark.
@shurunxuan are you able to share your appveyor.yml or any scripts you're using? I'd like to replicate the build and see if it freezes for me as well. |
@voltagex Sure. version: 1.0.{build}
image: Visual Studio 2017
configuration:
- Debug
- Release
platform:
- x86
- x64
before_build:
- nuget restore src/DSEngine/DSEngine.sln
install:
- cd C:\Tools\vcpkg
- git pull
- .\bootstrap-vcpkg.bat
- cd %APPVEYOR_BUILD_FOLDER%
- vcpkg integrate install
- vcpkg update
- vcpkg upgrade --no-dry-run
- cmd: if "%platform%"=="Win32" set VCPKG_ARCH=x86-windows
- cmd: if "%platform%"=="x86" set VCPKG_ARCH=x86-windows
- cmd: if "%platform%"=="x64" set VCPKG_ARCH=x64-windows
- vcpkg install boost:%VCPKG_ARCH%
- vcpkg install ffmpeg:%VCPKG_ARCH%
build:
project: src/DSEngine/DSEngine.sln
verbosity: minimal
cache: c:\tools\vcpkg\installed\ |
I've switched my appveyor to just cloning vcpkg, installing, and building ffmpeg in a powershell script. With my own minimal ffmpeg that means I can reproduce in ~7min, but for bisecting I'd rather just use the the upstream port. As far as RDPing into Appveyor, I tried that but I didn't see anything interesting. I saved a dump from process explorer while it was stuck. Nothing stands out to me, but maybe someone here sees something? If there's something else in particular I should look at I'll run RDP again; otherwise I'll continue with my bisect.
|
@wangli28 there's enough information now to remove the |
As the TheCycoOne points out msys2 change, appears to introduce gpg 2.1 which launches gpg-agent daemon process. The appveyor builds appear to be lingering awaiting that process to die. Our script for CorsixTH, I altered with a Stop-Process -Force -Name "gpg-agent" for a quick test just before it exits and the process continued as expected. Though running locally I didn't see the same as @shurunxuan. |
Platform: Windows
Package: ffmpeg:x64-windows & ffmpeg:x86-windows
Vcpkg version: 2018.11.23-nohash
Description:
I was trying to install ffmpeg (4.1.0) with vcpkg on Windows 10. The build seems to succeed, but after that vcpkg freezes and won't quit. I can still use ffmpeg after I force it to quit. While this is not quite a problem on my local machine, the CI builds will be blocked by this and won't continue.
Command Line:
vcpkg install ffmpeg:x86-windows
Command Line Output:
After that vcpkg freezes. The build was running for two hours when I copied the log.
The text was updated successfully, but these errors were encountered: