From: =?iso-8859-1?Q?Peter_Tr=F6ger?= <peter.troeger@hpi.uni-potsdam.de>
Sender: <owner-drmaa-wg@ggf.org>
To: "Ruben Santiago Montero" <rubensm@dacya.ucm.es>
Cc: "DRMAA Working Group" <drmaa-wg@gridforum.org>
References: <200603181416.03350.rubensm@dacya.ucm.es>
 <200603211155.00824.rubensm@dacya.ucm.es>
 <4420656E.1020806@hpi.uni-potsdam.de>
 <200603231154.56859.rubensm@dacya.ucm.es>
Subject: Re: [drmaa-wg] DRMAA TEST SUITE
Date: Thu, 23 Mar 2006 16:00:06 -0500
Message-ID: <44230C56.5020000@hpi.uni-potsdam.de>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00AB_01C6564A.984CB390"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcZOvM76P8wyV9lqRV6jpspnNA+aow==
In-Reply-To: <200603231154.56859.rubensm@dacya.ucm.es>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Apparently-To: hrabri@sbcglobal.net via 68.142.199.165;
 Thu, 23 Mar 2006 13:00:26 -0800
X-Originating-IP: [140.221.10.4]
X-Original-To: grdfm-drmaa-wg@mailbouncer.mcs.anl.gov
x-fsavag4mse-ts: dbb6c6d4fbd7d8b3
X-OriginalArrivalTime: 23 Mar 2006 21:00:01.0725 (UTC)
 FILETIME=[C082BED0:01C64EBC]

This is a multi-part message in MIME format.

------=_NextPart_000_00AB_01C6564A.984CB390
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

>> Our proposal is to remove the call of drmaa_wifaborted() for
>> ST_INPUT_FILE_FAILURE / ST_ERROR_FILE_FAILURE / ST_OUTPUT_FILE_FAILURE.
>> The drmaa_wait() call does not hurt (since all submitted jobs must be
>> waitable), but the crucial part is the testing for the result of
>> drmaa_synchronize(). After this change, I would expect the test cases to
>> be successful also on your system. In case of malicious input / output /
>> error files, the DRMAA implementation would only be expected to state a
>> job failure. This should work for all GridWay-supported systems, right ?
>> Could you accept this proposal ?
>>
> Sure. It make sense for me also.
> 
> There is also a validator in the state diagram (Section 2.6). I am just 
> wondering if a DRMAA implementation could just reject the jobs in these
tests 
> at submission with a DRMAA_ERRNO_DENIED_BY_DRM.

The spec is unclear here, since the description of the input / ouput / 
error parameters demands a particular job state - DRMAA_PS_FAILED. You 
can only have a job state when you have a job id. YOu can only have a 
job id when drmaa_run() was successfull. I really would like to have the 
opportunity of DRMAA_ERRNO_DENIED_BY_DRM also in this case, but then we 
have to relax the description of the according job template attributes.

Sounds like another issue for the next phone call. Hrabri ?

Regards,
Peter.


------=_NextPart_000_00AB_01C6564A.984CB390
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7036.0">
<TITLE>Re: [drmaa-wg] DRMAA TEST SUITE</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>&gt;&gt; Our proposal is to remove the call of =
drmaa_wifaborted() for</FONT>

<BR><FONT SIZE=3D2>&gt;&gt; ST_INPUT_FILE_FAILURE / =
ST_ERROR_FILE_FAILURE / ST_OUTPUT_FILE_FAILURE.</FONT>

<BR><FONT SIZE=3D2>&gt;&gt; The drmaa_wait() call does not hurt (since =
all submitted jobs must be</FONT>

<BR><FONT SIZE=3D2>&gt;&gt; waitable), but the crucial part is the =
testing for the result of</FONT>

<BR><FONT SIZE=3D2>&gt;&gt; drmaa_synchronize(). After this change, I =
would expect the test cases to</FONT>

<BR><FONT SIZE=3D2>&gt;&gt; be successful also on your system. In case =
of malicious input / output /</FONT>

<BR><FONT SIZE=3D2>&gt;&gt; error files, the DRMAA implementation would =
only be expected to state a</FONT>

<BR><FONT SIZE=3D2>&gt;&gt; job failure. This should work for all =
GridWay-supported systems, right ?</FONT>

<BR><FONT SIZE=3D2>&gt;&gt; Could you accept this proposal ?</FONT>

<BR><FONT SIZE=3D2>&gt;&gt;</FONT>

<BR><FONT SIZE=3D2>&gt; Sure. It make sense for me also.</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; There is also a validator in the state diagram =
(Section 2.6). I am just </FONT>

<BR><FONT SIZE=3D2>&gt; wondering if a DRMAA implementation could just =
reject the jobs in these tests </FONT>

<BR><FONT SIZE=3D2>&gt; at submission with a =
DRMAA_ERRNO_DENIED_BY_DRM.</FONT>
</P>

<P><FONT SIZE=3D2>The spec is unclear here, since the description of the =
input / ouput / </FONT>

<BR><FONT SIZE=3D2>error parameters demands a particular job state - =
DRMAA_PS_FAILED. You </FONT>

<BR><FONT SIZE=3D2>can only have a job state when you have a job id. YOu =
can only have a </FONT>

<BR><FONT SIZE=3D2>job id when drmaa_run() was successfull. I really =
would like to have the </FONT>

<BR><FONT SIZE=3D2>opportunity of DRMAA_ERRNO_DENIED_BY_DRM also in this =
case, but then we </FONT>

<BR><FONT SIZE=3D2>have to relax the description of the according job =
template attributes.</FONT>
</P>

<P><FONT SIZE=3D2>Sounds like another issue for the next phone call. =
Hrabri ?</FONT>
</P>

<P><FONT SIZE=3D2>Regards,</FONT>

<BR><FONT SIZE=3D2>Peter.</FONT>
</P>

</BODY>
</HTML>
------=_NextPart_000_00AB_01C6564A.984CB390--
