-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker runs gtc cpu backend #101
Conversation
|
||
RUN if [ ! -z `echo $GT4PY_OPTIONALS | grep cuda` ] ; then pip install cupy-cuda102==7.7.0 ; else echo Not installing cuda ; fi | ||
RUN pip install --no-cache-dir -c /constraints.txt "/gt4py${GT4PY_OPTIONALS}" && \ | ||
python3 -m gt4py.gt_src_manager install | ||
RUN python -m pip install --no-cache-dir -c /constraints.txt -e "/gt4py${GT4PY_OPTIONALS}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When installing without -e, on the first gtc backend run, it pulls the wrong version of gridtools again. But having -e skips that step. Unclear about this behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-e
is directing the GT source to be install alongside the python source, while without the -e
PIP installs into its own directory structure. The issue is that by default the source path is set to the one created by -e.
Another issue is that v36 via the src_manager is pulling GridTools |
launch jenkins |
1 similar comment
launch jenkins |
launch jenkins |
5 similar comments
launch jenkins |
launch jenkins |
launch jenkins |
launch jenkins |
launch jenkins |
Purpose
We cannot run gtc cpu backend in docker currently. This appears to be an issue with the version of grid tools libraries. This PR provides a temporary fix to run pytest with
gtc:gt:cpu_ifirst
backend.Infrastructure changes:
Checklist
Before submitting this PR, please make sure: