On Wed, Mar 23, 2011 at 03:00:55PM +0100, Michael Hanselmann wrote: > Am 23. März 2011 14:56 schrieb Iustin Pop <[email protected]>: > > On Wed, Mar 23, 2011 at 02:45:49PM +0100, Michael Hanselmann wrote: > >> + "jobs": [ > >> + (True, "8149"), > >> + (True, "21019"), > >> + (False, "Submission failed"), > > […] > > > > In this case, nothing exists that allows us to determine what the job > > that failed was composed of. > > > > We would need more data here; at a minimum, the list of opcode > > summaries. > > This was just an example,
Ah OK :) > the actual code in SubmitManyJobs uses the > string representation (“str(err)”) for failed submissions. If you > think that's still not enough SubmitManyJobs should be extended. What > do you think? I think that beside the reason for failure (i.e. str(err)), we need to know what the job that failed contained, hence my suggestion to list the summary of the jobs. That can be done from the caller of SubmitManyJobs, without changing the API. thanks, iustin
