#8 Killed job because of max wallclock time not logged

closed
None
5
2009-06-19
2009-06-18
No

When Opal kills a job because it has reached the max wall-clock time, it should log this fact (maybe in stdout or stderr?).

clem

Discussion

  • Luca Clementi

    Luca Clementi - 2009-06-19

    Opal relies on the underling job manager to enforce the wall clock.

    GRAM return successful even if the job hit the wall clock time, so there is not clean way for opal to detect this case.

    I added some some line in the doc to remember this...
    http://opaltoolkit.svn.sourceforge.net/opaltoolkit/?rev=414&view=rev

    Luca

     
  • Luca Clementi

    Luca Clementi - 2009-06-19
    • assigned_to: nobody --> lclement
    • status: open --> closed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks