-
I am using Pyinstaller to create an exe for my Bertopic model pipeline. I do not have any issues when I create and execute the exe in my VM GPU. Following is the error I am getting when the pipeline runs in the Azure DevOps pipeline. Shall I contact Azue, Pyinstaller, or here? Do not know. Please guide File "joblib\numpy_pickle.py", line 648, in load Versions: |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 6 replies
-
Have you tried adding |
Beta Was this translation helpful? Give feedback.
-
I suppose it is from the frozen application and not from the script because it is working in the VM. I am now working on the yml file (https://faun.pub/azure-pipelines-and-python-virtual-environments-fdc1089656db) to make sure it gets the same environment as it gets in the VP. I am supposing it is something related to Azurepipeline. Let me know if there is any other thoughts to it. |
Beta Was this translation helpful? Give feedback.
-
Yes, I build in VM. So I have created a VM through the EC2 instance, and all the process is done in it. The virtual environment is created, the list of libraries in the txt file in installed and the pyinstaller makes the exe and it runs successfully. |
Beta Was this translation helpful? Give feedback.
-
Hi, I am in touch with numba team too and the following is the comment I got [https://github.com/numba/numba/issues/9500] |
Beta Was this translation helpful? Give feedback.
-
Sure, Thanks! I will try Google Drive. |
Beta Was this translation helpful? Give feedback.
-
Reducing numba version to 0.58.1 worked :-) |
Beta Was this translation helpful? Give feedback.
Thanks for sharing the build directories. This confirms that your working and non-working builds were made in different environments (different versions of python, as well as different versions of python packags), and this leads to different behavior.
Specifically, the working build was made with
numba
0.58.1 or earlier, where vendorednumba.cloudpickle
package was directly importing thenumba.cloudpickle.cloudpickle_fast
module - therefore, this module was picked up by our import analysis, and collected into frozen application.The non-working build was made with
numba
0.59 or later, where vendorednumba.cloudpickle
was updated to v3.0.0; this version keepscloudpickle_fast
module around…