Re: [HTCondor-users] Making transfer_output / transfer_error depend on ExitCode

[John M Knoeller <johnkn@xxxxxxxxxxx>]

You could try

transfer_output = (ExitBySignal =?= True) || (ExitCode =!= 0)

(I assumed that you meant to invert the expression logic, since that's what you said he wanted)

Using =?= and =!=  will make this always evaluate to a Boolean - which gets you past the submission problem. 
But I'm not sure if it's actually going to *work* if the result of evaluation changes from false at submission time to true when the job exits with failure.

-tj

-----Original Message-----
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of Oliver Freyermuth
Sent: Tuesday, July 2, 2019 2:58 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] Making transfer_output / transfer_error depend on ExitCode

Dear HTCondor experts,

one of our users had a rather simple question, but it seems the solution is not as easy as expected (or I am missing something).

He wants to transfer job output (stdout) and error (stderr) back to the submit node via file transfer only if the job exits with an exit-code != 0.

I tried:
------------
transfer_output=(ExitBySignal == False) && (ExitCode == 0)
------------
but during submission, this yields:
------------
Submitting job(s) ERROR: transfer_output=(ExitBySignal == False) && (ExitCode == 0) is invalid, must eval to a boolean.
------------
I presume by design this must be evaluated on submission (to decide if the file permission checks need to be done, which were in the past done during submission by default).

Is there another way?

Cheers,
	Oliver