[drmaa-wg] DRMAA-WG April 4, 2006 call

Hrabri Rajic hrabri at sbcglobal.net
Mon Apr 3 01:18:03 CDT 2006


Mea culpa!

I have failed to synchronize my two accounts and have overlooked the latest
Peter's e-mail, so please consider the inlined proposal obsolete.

Hrabri



> -----Original Message-----
> From: owner-drmaa-wg at ggf.org [mailto:owner-drmaa-wg at ggf.org] On Behalf Of
> Hrabri Rajic
> Sent: Sunday, April 02, 2006 11:43 AM
> To: 'DRMAA Working Group'
> Subject: [drmaa-wg] DRMAA-WG April 4, 2006 call
> 
> *** new phone numbers ***
> *** new phone numbers ***
> 
> 
> The bi-weekly DRMAA call is scheduled for 16:00 UTC (8:00PDT - Pacific
> Daylight Time /10:00CDT/ 17:00 Central Europe). All Participants should
> use
> the following information to reach the conference call:
> 
> ------------------------------------
> * Toll Free Dial In Number for North America:   1 800 867-8609
> * Toll Free Dial In Number for Germany:         0 800 101-4546
> * Int'l Access/Caller Paid Dial In Number:      +49 069509594678
> * ACCESS CODE: 7223898
> ------------------------------------
> 
> Attachments to this email:
> 
>       - March 21 meeting minutes
> 
> 
> Meeting Agenda:
> 
> A. Meeting secretary for this meeting?
> 
> B. Acceptance of the March 21, 2006 meeting minutes
> 
> C. Admin
> 	- third chair update
> 
> F. Open/general issues discussion
>   - experience documents
>   - #1125 Tracker - see the included text at the end of the agenda
>   - Job suspension is different from triggering job rescheduling in Condor
>            (see attached  " "Re: GridWay Experience Report" mail)
>   - Status of the test suite
>       - post ver 1.0 issues
>       - handling exit status for bad input / ouput / error streams
>            (see attached "Re: [drama-wg] DRMAA TEST SUITE" mail)
>   - misc
> 
> 
> Cheers,
> 	Hrabri
> 
> 
> ------------------------- Tracker #1125 proposed change
> ----------------------------
> 
> Currently we have:
> "Evaluates into 'exited', a non-zero value if stat was returned for a job
> that terminated normally. A zero value can also indicate that although the
> job has terminated normally an exit status is not available or that it is
> not known whether the job terminated normally. In both cases
> drmaa_wexitstatus() SHALL NOT provide exit status information.
> A non-zero 'exited' value indicates more detailed diagnosis can be
> provided
> by means of drmaa_wifsignaled(), drmaa_wtermsig(),drmaa_wexitstatus(), and
> drmaa_wcoredump()."
> 
> It was proposed (Hrabri's adaptation of Peter's latest proposal) to change
> it to
> 
> "Evaluates into 'exited' a non-zero value if stat was returned for a ended
> job
> that either failed after running or finished after running (see section
> 2.6).
> A non-zero 'exited' value indicates more detailed diagnosis can be
> provided
> by
> means of drmaa_wifsignaled(), drmaa_wtermsig(),drmaa_wexitstatus(), and
> drmaa_wcoredump() functions.
> A zero result for the 'exited' parameter either indicates that
>    1) although it is known that the job was running, more information is
> not
> available
>    2) it is not known whether the job was running
> 
> In both cases drmaa_wexitstatus() SHALL NOT provide exit status
> information."
> 

-------------- next part --------------
An embedded message was scrubbed...
From: "Rajic, Hrabri" <hrabri.rajic at intel.com>
Subject: FW: [drmaa-wg] DRMAA TEST SUITE
Date: Thu, 30 Mar 2006 08:09:47 -0500
Size: 37231
Url: http://www.ogf.org/pipermail/drmaa-wg/attachments/20060403/6cb2d849/attachment.mht 


More information about the drmaa-wg mailing list