[Condor-users] Is this a feature or a bug in Condor 6.7.19?

[Gabriel Mateescu <gabriel.mateescu@xxxxxx>]

Hello, 

I noticed that the mapping of the 
job's stdout has changed from 
Condor 6.7.17 to 6.7.19 in an 
important way. 



1. "Old" (6.7.17) mapping for Condor-G jobs for GT4 
   resources:

   the job attribute

      Out = /path/to/file 

   was mapped to 

<stdout>${GLOBUS_SCRATCH_DIR}/job_HASH/file</stdout>

<fileStageOut>
  ...
  <sourceUrl>
  file:///${GLOBUS_SCRATCH_DIR}/job_HASH/file
  </sourceUrl>
  ...
</fileStageOut>

where ${GLOBUS_SCRATCH_DIR}/job_HASH is also the value 
of the <directory> element. 

   


2. "New" (Condor 6.7.19) mapping for Condor-G jobs for GT4 
   resource:

   The job attribute

      Out = /path/to/file 

   is mapped to 

<stdout>${GLOBUS_SCRATCH_DIR}/job_HASH/file</stdout>

<fileStageOut>
  ...
  <sourceUrl>
  file:///path/to/file
  </sourceUrl>
  ...
</fileStageOut>


This new behavior seems to me less suitable than 
the old behavior, because now the <sourceUrl> path 
does not match <stdout>, which is still mapped to 
${GLOBUS_SCRATCH_DIR}/job_HASH, and thus one 
cannot use absolute paths in the Out specification 
any more; in other words, the staged out file 
will be an empty file rather than stdout. 


But what I do not know is if the new behavior has 
been done intentionally or if it is a bug. 

Thank you.
Gabriel