Open jack-morrison opened 6 months ago
I suspect that the exec step of the SSH scheduler fails and the pull is ignored silently. Maybe this part is at fault:
As each subsequent step will only be launched if it's previous has succeeded. This function will return however, whenever the last run step has finished and will not check that the remaining one was not run. The _poll_job()
below treats that properly.
Opening after discussion with @vkarak. It sounds like we've both hit some issues with auto-detection over SSH at one time or another.
It appears that when using the SSH scheduler, if the remote execution of
rfm-detect-job.sh
fails, thersync
back to the launching host is not run.Here's a recent log+traceback where I observe
rfm-detect-job.sh
failing on the remote host over SSH (for self-inflicted reasons):I'm not sure what the desired behavior would be when remote execution of
rfm-detect-job.sh
fails - maybe an error, reflective of the Python FileNotFoundError, instead of the WARNING that ReFrame writes (shown below)? Maybe the returningrsync
still happens?