It seems wrong to rebuild the entire controls conda env on s3df, a system without controls
How Has This Been Tested?
I set my PATH to my clone of engineering tools and removed the previous tagged engineering tools from my PATH. Then I verified functionality and failure modes on both systems:
Basic functionality (using get_lastRun): It's the same results in each system which is a good sign.
Error state if the python interpreters are both not found (by modifying the script to look for the wrong ones): It tells you why it isn't running and what it tried to use.
zlentz@psbuild-rhel7-02:~/.../engineering_tools/scripts(master +)$ ./get_lastRun -H xpp
No known python executable is available! Tried all of /cds/group/pcds/pyps/conda/py36/envs/pcds-3.4.0/bin/pythonasfd /sdf/group/lcls/ds/ana/sw/conda1/inst/envs/ana-4.0.60-py3/bin/python
[zlentz@sdfiana008 scripts]$ ./get_lastRun -H xpp
No known python executable is available! Tried all of /cds/group/pcds/pyps/conda/py36/envs/pcds-3.4.0/bin/python /sdf/group/lcls/ds/ana/sw/conda1/inst/envs/ana-4.0.60-py3/bin/pythonasdfasd
Error codes from get_info.py are properly passed to get_info:
Description
get_info
toget_info.py
and wrap in aget_info
bash scriptget_info
Motivation and Context
How Has This Been Tested?
I set my
PATH
to my clone of engineering tools and removed the previous tagged engineering tools from myPATH
. Then I verified functionality and failure modes on both systems:Basic functionality (using get_lastRun): It's the same results in each system which is a good sign.
Basic functionality using the script directly seems to work too:
Error state if the python interpreters are both not found (by modifying the script to look for the wrong ones): It tells you why it isn't running and what it tried to use.
Error codes from get_info.py are properly passed to get_info:
Where Has This Been Documented?
Only here, in the release notes later, and in the jira ticket