After switching to using pex generated lockfile, m...
# general
After switching to using pex generated lockfile, my tests take too long to run. It's like 5 times (went from ~6 mins to ~29 mins). I am using pants 2.11.0 It's the exact set of dependencies as before but now I am using multiple resolves. Any debugging pointers to figure out why? This is the earlier thread
The only thing I see in the log is that it's a long running task
Copy code
1:34:43.13 [INFO] Long running tasks:

  88.95s    Building 16 requirements for requirements.pex from the 3rdparty/pyfleet_vehicle_spec.lock resolve: PyYAML<6.0.0,>=5.4.1, SQLAlchemy<2.0.0,>=1.4.25, Unidecode<2.0.0,>=1.3.2, awswrangler<3.0.0,>=2.14.0; python_version >= "3.9" and python_version < "3.11", boto3<2.0.0,>=1.21.20, dynamic-yaml<2.0.0,>=1.3.0, fastapi<0.71.0,>=0.70.0, loguru<0.6.0,>=0.5.3, mangum<0.13.0,>=0.12.3, numpy>=1.20.0, pandas<2.0.0,>=1.3.3, prophet@ git+<>, pytest<7.0.0,>=6.0, python-jose[cryptography]<4.0.0,>=3.3.0, spacy<4.0.0,>=3.1.3, uvicorn<0.16.0,>=0.15.0
Do you intentionally not pin prophet to a commit? That git requirement currently floats.
I am using the main branch. Should I also provide the commit?
I suppose that would make sense
It depends what you want. Do you actually want every new commit that lands on main?
This may or may not solve your problem, but without a pin, this has to be slow in any conceivable world.
not really! I have to use the source because they had some fix which they are taking forever to release on pypi. I can fix it to any commit after that.