The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.
Revision history for Perl extension LSF.

0.1  Mon Feb 18 12:10:31 2002
	 First release.
     
0.2  Wed Apr 03 10:03:25 2002
     Second release. Includes LSF::JobManager
      
0.21 Thu Apr 04 10:40:57 2002
     Simplified the test suite. A couple of things have been superceeded by the
     addition of LSF::JobManager (and i still need to write a proper test suite)

0.3  Thu Apr 04 17:20:55
     Now checks the version of LSF at startup. If it is version 4 then the 
     stdout/stderr of the bsub command is swapped. Required module System2 has
     problems when called in a BEGIN block so i have switched to IPC::Run
     
0.4  Sun Apr 08 19:53:02
     Errors can now be thrown via the RaiseError directive / class method.
     The printing of the LSF command line stdout / stderr is separated out
     and controlled by the PrintOutput and PrintError directives / class methods

0.5  Fri Jul 19 11:05:17
     LSF::JobInfo is now defunct. The information obtained from the bjobs 
     command is expunged from the LSF logs far too quickly to be reliably
     available in a long running batch environment. Replacing it is
     LSF::JobHistory which calls and parses the bhist command.

     Removed the jobs_with_status method from the LSF::JobManager module since
     this didn't have a good rationale behind it and the exit status is now
     obtainable from the LSF::JobHistory object.

     Added a clear method to the LSF::JobManager class so that the jobs in a 
     job manager can be cleared and it can be reused.

     Added a history method to the LSF::Job class so that an LSF::JobHistory 
     object can be obtained for a job.
     
     Removed the info method from the LSF::Job class
     
     The LSF::JobManager->wait_all_children method now uses LSF::JobHistory to
     pre-cache the results of the bhist command for each job. There are hugely 
     significant performance benefits to calling a single bhist command line for
     all jobs as opposed to once for each job.