We are encountering the following warning in our CI builds:
Warning: Janus: venv directory '/home/runner/work/metta-wam/metta-wam/venv' does not contain "/home/runner/work/metta-wam/metta-wam/venv/lib/python3.10/site-packages"
This indicates that the virtual environment may not be using Python 3.10 as expected, which could be causing issues during the build process.
Potential Cause:
It seems that the virtual environment is either:
Not being built using Python 3.10, or
The Python version in the virtual environment differs from what is expected (3.10).
Steps to Reproduce:
Run the CI workflow.
Observe the warning message about the virtual environment.
Expected Behavior:
The virtual environment should be built using Python 3.10, and the correct directory (/home/runner/work/metta-wam/metta-wam/venv/lib/python3.10/site-packages) should exist without triggering any warnings.
Suggested Fix:
Ensure that the correct Python version (3.10) is being used when creating the virtual environment in the CI pipeline.
Double-check the CI configuration to verify that the Python version is explicitly set to 3.10.
Environment:
CI Platform: GitHub Actions
Python Version: Expected 3.10
Affected builds: All recent builds
Additional Context:
This warning may cause issues with dependencies or environment setup, so it is important to address it to prevent potential build failures or inconsistent behavior in the CI pipeline.
We are encountering the following warning in our CI builds:
This indicates that the virtual environment may not be using Python 3.10 as expected, which could be causing issues during the build process.
Potential Cause:
It seems that the virtual environment is either:
Steps to Reproduce:
Expected Behavior:
The virtual environment should be built using Python 3.10, and the correct directory (
/home/runner/work/metta-wam/metta-wam/venv/lib/python3.10/site-packages) should exist without triggering any warnings.Suggested Fix:
Environment:
Additional Context:
This warning may cause issues with dependencies or environment setup, so it is important to address it to prevent potential build failures or inconsistent behavior in the CI pipeline.