Open aulemahal opened 1 year ago
Hi, just to quickly address one of your points
However,
cylc__job__inst__user_env()
seems to never be called anywhere.
It is called here
- The
python-job.settings
"hack" looks like it does nothing ? Shouldn't it have added the correctcylc
to the path in my first try ?
The PYTHONPATH
manipulation wasn't doing anything and has been removed on master. The PATH
manipulation ensures the python libraries from the Cylc environment are available to the job at run time, however it does not ensure the cylc
commands are available, which is the responsibility of the wrapper script.
Description
I was following the cylc tutorial and was unable to make the
runtime-introduction
practical work.On my first try, the job did run (the log shows the python code was executed and the csvs are done), but it seems it can't communicate back to the scheduler.
Reproducible Example
Test 1 - just follow the basic instructions
In the GUI, I see that all jobs are submitted, but none ever go beyond that stage. Looking at a log I see:
Interestingly, I note that some PATH manipulation happens in
~/cylc-src/runtime-introduction/etc/python-job.settings
, resulting in the following function added to~/cylc-run/runtime-introduction/run1/log/job/20000101T0000Z/get_observations_aldergrove/01/job
:(
/exec/prod2/.conda
is where my conda envs are installed)However,
cylc__job__inst__user_env()
seems to never be called anywhere. I.e. output ofgrep -r cylc__job__inst__user_env ~/cylc-run/runtime-introduction/
only shows the declaration of that function in the generated job files).Test 2 -
cylc
wrapperAfter that try, I realized I hadn't read the Managing environments section of the installation doc (because it was under "Advanced installation"). And I started from the beginning again:
And this time it worked!
Conclusion
I was able to make it run, but I believe my experience raises the following issues:
python-job.settings
"hack" looks like it does nothing ? Shouldn't it have added the correctcylc
to the path in my first try ?mamba create
. Should I override withCYLC_ENV_NAME
, even though this is not recommended ?