Why does it seem like this step is not cached by P...
# general
c
Why does it seem like this step is not cached by Pants? (for a
./pants run ..
on 2.13.0):
Copy code
59.01s Building 45 requirements for src.python/.../some.pex from the 3rdparty/python/lockfiles/default.txt resolve: Django==3.2.16, JPype1==0.7, ...
As it is rather time consuming (~60s) it’s a bit of a waste to wait at every time I want to run that .pex app.. Asking to see if I’ve missed something obvious, or if it sounds like a bug worth investigating further..
h
Seems like a bug. That should be cached!
f
Can you run with
-ldebug
and capture the log line for the
Process
that is being invoked to make the pex? (The goal is to be able to see exactly what is contributing to the cache key.)
c
bah, I did see this several times, but now when I run with
-ldebug
it uses a cached version.. go figure. I’ll keep a look out for it…