[Swift-devel] provider-condor submit file generation

[Mihael Hategan]

I would strongly encourage the use of a debugger in such cases.

In the case below an entirely different provider is used. It's in
provider-localscheduler. The relevant files are in 
org.globus.cog.abstraction.impl.scheduler.condor.

The part that deletes the script file is in
org.globus.cog.abstraction.impl.scheduler.common. Somewhere in start().
I'm not sure, but I think Mike has added a condition around file
removal, which disables it if you say "debug=true" in
provider-condor.properties.


On Mon, 2010-05-17 at 19:14 -0500, Allan Espinosa wrote:
> I was poking around the provider-condor source tree today.
> 
> provider-condor/src/org/globus/cog/abstraction/impl/execution/condor/DescriptionFileGenerator.java:33+:
> ...
>     private static void constructDescriptionFile(File descriptionFile,
> Task task)
>             throws IOException {
>         JobSpecification specification = (JobSpecification) task
>                 .getSpecification();
>         FileWriter fileWriter = new FileWriter(descriptionFile);
>         fileWriter.write("#####################################\n");
>         fileWriter.write("# Task ID: " + task.getIdentity().toString() + "\n");
>         fileWriter.write("#####################################\n\n");
> 
>         String executable = specification.getExecutable();
>         if (executable != null) {
>             fileWriter.write("Executable = " + executable + "\n");
>         }
> 
>         String argumentString = specification.getArgumentsAsString();
>         argumentString = argumentString.replaceAll("\\\"", "\\\\\"");
>         if (argumentString != null) {
>             fileWriter.write("Arguments = " + argumentString + "\n");
>         }
> ..
> 
> 
> But when I looked at a generated condor-g job in my workflow i got:
> universe = grid
> grid_resource = gt2 ff-grid.unl.edu/jobmanager
> stream_output = False
> stream_error  = False
> Transfer_Executable = false
> output = /home/aespinosa/workflows/cybershake/condorg/res_testjob.submit.stdout
> error = /home/aespinosa/workflows/cybershake/condorg/res_testjob.submit.stderr
> log = /home/aespinosa/workflows/cybershake/condorg/res_testjob.submit.log
> 
> remote_initialdir =
> /panfs/panasas/CMS/data/engage-aespinosa/swift/postproc-fireflyg_small
> executable = /bin/bash
> arguments = /panfs/panasas/CMS/data/engage-aespinosa/swift/postproc-fireflyg_small/shared/_swiftwrap
> extract-mo6464sj -jobdir m -scratch  -e
> /panfs/panasas/CMS/app/engage-aespinosa/JBSim3d/bin/jbsim3d -out
> stdout.txt -err stderr.txt -i -d
> TEST|158/0|panfs/panasas/CMS/data/engage-aespinosa/swift/158/0 -if
> TEST/TEST_fy_644.sgt|TEST/TEST_fx_644.sgt|158/0/158_0.txt.variation-s0001-h0000
> -of panfs/panasas/CMS/data/engage-aespinosa/swift/158/0/TEST_158_0_subfy.sgt|panfs/panasas/CMS/data/engage-aespinosa/swift/158/0/TEST_158_0_subfx.sgt
> -k  -cdmfile fs.data -status files -a stat=TEST extract_sgt=1
> slon=-118.286 slat=34.0192
> rupmodfile=158/0/158_0.txt.variation-s0001-h0000
> sgt_xfile=TEST/TEST_fx_644.sgt sgt_yfile=TEST/TEST_fy_644.sgt
> extract_sgt_xfile=panfs/panasas/CMS/data/engage-aespinosa/swift/158/0/TEST_158_0_subfx.sgt
> extract_sgt_yfile=panfs/panasas/CMS/data/engage-aespinosa/swift/158/0/TEST_158_0_subfy.sgt
> notification = Never
> leave_in_queue = TRUE
> queue
> 
> I was at least expecting to the the line to start with '##### ...\n #
> Task : ..." .  Is there another place I should poke around to figure
> out the jobspec to condor submit file? Like where does "jobType=grid"
> get translated to "Universe=grid"?
> 
> Thanks!
> -Allan
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel