[torquedev] [Bug 51] Fix for r3466 commit

bugzilla-daemon at supercluster.org bugzilla-daemon at supercluster.org
Mon Feb 22 21:00:22 MST 2010


--- Comment #4 from Simon Toth <SimonT at mail.muni.cz> 2010-02-22 21:00:21 MST ---
> When you say completely breaks the server on default setup, what do you mean? I
> am able to checkout a clean branch, run the setup, make a nodes file, and run
> jobs. 

Well, I can't run any jobs. By default (nothing is set) the Job ID stored with
the job is the full hostname one: jobid.servername.hostname but when nothing is
set the get_correct_jobname returns jobid.servername (string comparison then
simply fails). It may work if the machine you are testing it on does not have a

> At the same time, this isn't going to add much time to job lookup, since job
> lookup has to scroll through all of the jobs known to that server, and this
> just adds a function call and some checking. I'm open to both possibilities.
> Please let me know your thoughts.

Torque is not CPU bound, the performance limitations are elsewhere.

Well, I have a big problem with this feature, because apart from the fact, that
I can't run any jobs on the server by default it isn't compatible with many
other features I implemented into Torque in the last year.

If the feature would be part of Trunk, or if it would be optional (configure
flag), then I would be much more happy.

Configure bugmail: http://www.clusterresources.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

More information about the torquedev mailing list