Python jobs on PS platform: executable issues
Hello @dbeltran and @bdepaula,
Autosubmit Version
4.1.x (tested .5 and .6)
Which task has issues?
autosubmit run
Summary
When a task is run with type python
on a PS platform, it is executed with the command nohup python <filename>
, which can easily break due to not finding the correct executable. This is also the case, if an executable is supplied with the EXECUTABLE
field.
Steps to reproduce
autosubmit expid -dm -H <PSARCH> -d "Test exp for python bug report".
- Add
TYPE: python
to one job, e.g.INI
. - OPTIONAL: Add
EXECUTABLE: /path/to/my/python3
to the job autosubmit create <expid>
autosubmit run <expid>
What is the current bug behavior?
The job INI
fails with the error nohup: failed to run command 'python': No such file or directory
.
What is the expected correct behavior?
It should use python3
or the provided executable to run the job.
Relevant logs and/or screenshots
Autosubmit log report (full_log.txt):
2024-05-31 14:20:49,895 Submitting job with the command: timeout 18000 nohup python /work/bb1215/b382013/a01f/LOG_a01f/a01f_20000101_fc0_INI.cmd > /work/bb1215/b382013/a01f/LOG_a01f/a01f_20000101_fc0_INI.cmd.out.0 2> /work/bb1215/b382013/a01f/LOG_a01f/a01f_20000101_fc0_INI.cmd.err.0 & echo $!
Any other relevant information
The relevant code part is here:
https://earth.bsc.es/gitlab/es/autosubmit/-/blob/master/autosubmit/platforms/paramiko_platform.py#L1187