Closed rsdunlapiv closed 3 years ago
Another important detail:
rocky@rocky-Latitude-E5570:~/esmfdev/esmf-profiler.v1$ find $PWD/dependencies/INSTALL/babeltrace2-2.0.4 -type d -name "site-packages"
/home/rocky/esmfdev/esmf-profiler.v1/dependencies/INSTALL/babeltrace2-2.0.4/lib/python3.9/site-packages
/home/rocky/esmfdev/esmf-profiler.v1/dependencies/INSTALL/babeltrace2-2.0.4/lib/python3.8/site-packages
It seems that I have bindings installed for two versions of Python3 which is probably throwing off the test. Solutions might be to install only one version or to fix the test so that it allows multiple installations. But we will have to choose only one to use for setting the environment variables.
@rsdunlapiv At first guess, it seems like installs are going to 3.9 before the virtual environment activation and then 3.8 after.
Found it!
The INSTALL directory was incorrectly committed to the repo: https://github.com/esmf-org/esmf-profiler/tree/main/dependencies/INSTALL
This is where the extra Python install came from.
It should be removed. We will also need a v.1.1 tag since this will impact users.
This has been resolved in the development branch, and as @rsdunlapiv mentioned above, was caused by keeping the uncompressed dependency directories in the repo.
Removing them (leaving only the compressed files) has resolved the issue.
Describe the bug
After running
./install_dependencies.sh && ./install.sh
on my system, I see an error message that it failed to find the Python Babeltrace2 module:Strangely, that path does exist:
So it may be that the check itself is wrong.
This results in existing the install.sh script early, so that the LD_LIBRARY_PATH and PYTHONPATH env. variables are not appended to the venv/bin/activate script. The then leads to the test failure:
To Reproduce
Run the install script. Not sure if this is an issue specific to my machine.
Expected behavior
The install.sh script should correctly locate the bt2 python bindings and not exit early.
Desktop (please complete the following information):