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

New to vcpkg - install of PCL taking 6+ hours #14280

Closed
ericwilliamsneu opened this issue Oct 28, 2020 · 14 comments
Closed

New to vcpkg - install of PCL taking 6+ hours #14280

ericwilliamsneu opened this issue Oct 28, 2020 · 14 comments
Assignees
Labels
category:question This issue is a question

Comments

@ericwilliamsneu
Copy link

vcpkg appears to hang on various steps
This is my first attempt to use vcpkg, so I'm guessing the issue may be PEBKAC, but it doesn't feel that way. After having cloned the repository, bootstrapped it, installing Visual Studio 2019 Community (with C++ desktop support), and installing the latest and greatest version of PowerShell (v7), I attempted to install my first package (the Point Cloud Library).

The tool actually appears to be working, but so far it's taken over 6 hours. It appears that either the package manager itself, PowerShell, or something else has "hung up" and take an indefinite nap on few packages. What I've found by luck and chance is that if I spam enter into the PowerShell terminal the whole act will "wake back up" and start chugging along again. Some dependencies are flying by... some may take infinitely long unless I hit it with the enter-hammer.

Some favorites so far (from the program output in the PowerShell console that's actively running):

  • Elapsed time for package openssl-windows:x86-windows: 5.192 h (just sat there, sleeping while I got some sleep myself, I suppose)
  • Elapsed time for package boost-filesystem:x86-windows: 11.75 min
  • Elapsed time for package boost-exception:x86-windows: 21.59 min

Most of the rest of the packages are taking extremely reasonable times between 5 seconds and 30 seconds.

The most common place in the routine for each package for the "hang up" is right after -- Configuring x86-windows.

Environment

  • OS: Windows 10 Build 18363
  • Compiler: Visual Studio 2019 with C++ (Community)
@JackBoosY
Copy link
Contributor

Can you confirm that your PowerShell is not hung up?
Such as:
image

@JackBoosY JackBoosY added the category:question This issue is a question label Oct 29, 2020
@ericwilliamsneu
Copy link
Author

Can you confirm that your PowerShell is not hung up?
Such as:
image

Confirmed - the PowerShell window title is just "PowerShell 7(x64)" and nothing is selected. I've retried this process about 4 times now, it keeps getting a little further before a massive unrecoverable hang. I've seen this issue has been raised before (#7251, #3391, etc).

@JackBoosY JackBoosY added category:vcpkg-bug The issue is with the vcpkg system (including helper scripts in `scripts/cmake/`) requires:repro The issue is not currently repro-able and removed category:question This issue is a question labels Oct 30, 2020
@JackBoosY
Copy link
Contributor

cc @BillyONeal if he has some ideas.

@BillyONeal
Copy link
Member

The ones reported before that I know about were all about vcpkg_acquire_msys we fixed by removing msys' pacman from the process.

It is likely that one of the dependent ports is trying to prompt for input or something like that, but that isn't something we have seen ourselves...

@JackBoosY JackBoosY added category:question This issue is a question and removed category:vcpkg-bug The issue is with the vcpkg system (including helper scripts in `scripts/cmake/`) requires:repro The issue is not currently repro-able labels Nov 6, 2020
@JackBoosY
Copy link
Contributor

By reading the information you provided again, I believe that the build process is NOT really a hang, but a long time.
Can you provide the time from entering the installation command to Configuring x86-windows and from Configuring x86-windows to Installing x86-windows?

@JackBoosY JackBoosY added the requires:more-information This Issue requires more information to solve label Nov 6, 2020
@ericwilliamsneu
Copy link
Author

@JackBoosY I attempted to install the library on another machine with the intention of capturing the requested data, but unfortunately the problem shifted on this new machine. I was again required to hit enter to advance the process at certain points, but this time it would usually be after a build step, not a configure step. I'd watch the CPU usage on the machine skyrocket during the build as expected, but then it would die down to a nominal level. Several packages "hung" at this point (after the build had clearly completed, based on CPU usage) and the process did not advance until I hit enter. Immediately upon hitting enter, the process would leap forward. I'm starting to wonder if this could be a Powershell 7 problem, not a VCPKG problem.

I understand without the ability to duplicate this is impossible to investigate and squash. I'm amazed at the level of engagement you and the rest of the team have with the userbase. Thanks for providing and supporting a great tool. I don't know if you want to close this issue or leave it open with the more-information tag.

@JackBoosY
Copy link
Contributor

@ericwilliamsneu Can you provide the content before and after hang up in the install log?

@mikedld
Copy link

mikedld commented Jan 10, 2021

For me, downloading of Strawberry Perl (OpenSSL's build dependency) is going way too slow (under 50 KiB/s with ZIP itself being about 140 MiB) and that's what is causing OpenSSL build to take a long time. I ended up downloading (with axel in 50 threads) and caching Strawberry Perl's ZIP file manually, and then copying it into downloads/ subdirectory before vcpkg starts downloading it on its own. Not sure why the speed is that low, but it might make sense to report this to them and maybe provide an alternative download location pointing to some vcpkg or github server to speed things up.

@JackBoosY
Copy link
Contributor

@mikedld We tend to use github repo, but because some ports do not provide mirrors to github, or the version on github is too low compared to the official website, this caused this problem.

@mikedld
Copy link

mikedld commented Jan 11, 2021

I get that @JackBoosY, just thought you might be able to mirror it (or find an existing faster mirror)...

@JackBoosY
Copy link
Contributor

Strawberry Perl only provides its binary on the official website, not github.

@JackBoosY
Copy link
Contributor

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.

@ericwilliamsneu
Copy link
Author

ericwilliamsneu commented Apr 5, 2021 via email

@mzayarnyuk
Copy link

For me, downloading of Strawberry Perl (OpenSSL's build dependency) is going way too slow (under 50 KiB/s with ZIP itself being about 140 MiB) and that's what is causing OpenSSL build to take a long time. I ended up downloading (with axel in 50 threads) and caching Strawberry Perl's ZIP file manually, and then copying it into downloads/ subdirectory before vcpkg starts downloading it on its own. Not sure why the speed is that low, but it might make sense to report this to them and maybe provide an alternative download location pointing to some vcpkg or github server to speed things up.

wow interest post; they fix it or not....
have slow arm build

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
Projects
None yet
Development

No branches or pull requests

5 participants