- removed comment
SimFactory does not use the submit script defined in a machine
When building a configuration, simfactory is supposed to add the default submission script for a machine to the configuration so that it can be submitted. Currently, simfactory does not do this. I have to specify the --submitscript option by hand on the command line when I build.
Keyword: regression
Comments (7)
-
reporter -
- removed comment
Is this just the submit script, or is this also the run script? Some machines (workstations) don't support job submission, and therefore the submit script is optional.
-
reporter - removed comment
It is only the submit script. OK, so it can't give an error message if no submit script is present, as there might not be a submit script defined for a workstation. However, if the build command cannot determine what machine it is building for, it should give an error, rather than omit the submit script, I think.
-
- removed comment
Since it figured out the run script, I wonder why it didn't figure out the submit script as well. Seems it gave up too quickly assuming a submit script isn't necessary.
-
reporter - removed comment
The same thing just happened to me on Kraken as well, so it's not a Datura-specific problem. It might be a problem with remote submission.
-
reporter - removed comment
And on Kraken it's not figuring out the run script either. Maybe I had told it the run script for Datura in my first test yesterday. So in fact it doesn't seem to be able to figure out either.
-
- changed status to resolved
- removed comment
this problem has been corrected as of revision r1233.
- Log in to comment
Barry mentioned that this might be because I am using remote submission with Datura, and the --machine entry might not be propagated to the build command, so it doesn't know what submit script to use. If that is the case, it should give an error message that it doesn't know what submit script to use - it should never create a configuration with no submit script.