You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is a bug per se, but it was surprising and is probably at least a documentation issue. Using Conan 2.3, I was working on my update to conan 2.0 and conan lock create was taking a couple seconds for each combination, and I have 5-platforms7-conan-files2-configs...taking a total of ~330 seconds. Adding --build="*" sped it up to ~30 seconds. The additional time appears to be in "Computing necessary packages". It's unclear to me why locking cares what packages are in the remote?
How to reproduce it
No response
The text was updated successfully, but these errors were encountered:
Thanks for your report.
I think this might be expected for cases where there are a ton of tool_requires, that are not really installed locally in the current cache.
Can you please report a bit more about the problem, for example, how many dependencies are in each configuration, I guess that is assuming a blank cache and things are being downloaded, or even when the cache is populated?
Describe the bug
I'm not sure if this is a bug per se, but it was surprising and is probably at least a documentation issue. Using Conan 2.3, I was working on my update to conan 2.0 and
conan lock create
was taking a couple seconds for each combination, and I have 5-platforms7-conan-files2-configs...taking a total of ~330 seconds. Adding--build="*"
sped it up to ~30 seconds. The additional time appears to be in "Computing necessary packages". It's unclear to me why locking cares what packages are in the remote?How to reproduce it
No response
The text was updated successfully, but these errors were encountered: