On 09/05/2012 02:32 PM, Miguel Méndez wrote:
> Sorry, that link is for code's latest version. It's a bit different for the
> one I sent you.
Hi Miguel,
Yes, thanks, it is easy to believe that the code sets
the value to one, according to one of the "if" cases
that you showed.
I can not see any problems with the specifics of a
"scontrol show job" on the jobs, that get the
maximum value instead of the lowest. (Perhaps some
values, like the begin value, are not always correctly
initiated in some other part of the code?)
I can not see anything about bug fixing of Age
Priority calculations in the NEWS file of next
version, 2.4.2.
If I am very lucky, the changed code might indicate
that someone already is working on fixing a
bug that I am now suffering from?
Cheers,
-- Lennart Karlsson
UPPMAX, Uppsala University, Sweden
http://www.uppmax.uu.se
