[torquedev] TORQUE 2.5.8 release candidate
knielson at adaptivecomputing.com
Mon Aug 15 09:09:12 MDT 2011
----- Original Message -----
> From: "Martin Siegert" <siegert at sfu.ca>
> To: "Torque Developers mailing list" <torquedev at supercluster.org>
> Cc: "Nathan Burton" <nburton at adaptivecomputing.com>, "Zane Westover" <zwestover at adaptivecomputing.com>, "Torque Users
> Mailing List" <torqueusers at supercluster.org>, "Jason Booth" <jbooth at adaptivecomputing.com>, "Rick McKay"
> <rmckay at adaptivecomputing.com>, "Ryan Chabot" <rchabot at adaptivecomputing.com>
> Sent: Sunday, August 14, 2011 1:56:37 PM
> Subject: Re: [torquedev] TORQUE 2.5.8 release candidate
> Hi Ken,
> On Sat, Aug 13, 2011 at 11:23:41PM -0600, Ken Nielson wrote:
> > There is a release candidate for TORQUE 2.5.8 available.
> > The main item fixed for this release was a bug in TORQUE with the
> > procct resource. procct is intended to use on queues to be able to
> > manage jobs based on the number of processors requested. The procct
> > resource is intended to be strictly internal to torque. However, if
> > a job gets deferred in a routing queue the procct resource is still
> > in the Resource_List of the job and is passed to the scheduler. The
> > scheduler interprets the word procct as a generic resource and the
> > job cannot be run because there is no generic resource named procct.
> > As a result the job remains stuck in the queue and is never selected
> > to be run.
> > The snapshot can be downloaded at
> > http://www.clusterresources.com/downloads/torque/snapshots/torque-2.5.8-snap.201108132311.tar.gz
> > If you are having a problem with the procct in the scheduler please
> > download this snapshot and let us know if it helps.
> > Regards
> > Ken Nielson
> There is a problem with this snapshot when a job is submitted with
> -l procs=x
> (and no nodes specification). In that case the job is aborted with
> initialize_procct: Could not get nodes entry from Resource_List.
> initialize_procct should terminate only if neither nodes nor procs are
> specified. Patch attached.
> The remainder of the patch is necessary to make torque compile when
> configured with --enable-gcc-warnings.
> Martin Siegert
> Simon Fraser University
The patch is in and being tested. I will post another release candidate shortly.
More information about the torquedev