On 31/05/16 22:21, Riccardo Murri wrote:
Hi Gizo,
([email protected], Mon, May 30, 2016 at 03:23:25PM +0200:)
now that works, thank you.
Good to know!
Though I had to deactivate the function _check_version in
../easybuild/tools/job/gc3pie.py to avoid the error
eb Bonnie++-1.03e-goolf-1.4.10.eb -r -f --job
ERROR: Failed to parse GC3Pie version string 'development version (SVN $Revision$)' using
pattern ^(?P<version>\S*) version \(SVN \$Revision: (?P<svn_rev>\d+)\s*\$\)
So I guess I have installed the gc3pie dev version not quit correctly.
No, it;s the check that EB does that is nowadays incorrect ;-) GC3Pie
has switched from SVN to Git ...
OK, we'll need to fix that then. :-)
Originally the problem was not related to the torque version, instead to not
complete input to tracejob command I have given. Sorry about that.
As it seems currently gc3pue is using only torque server log to grab a job
completion status('S' records in the output),
while the same info is available in job accounting ('A' records in the same
output) files too.
Once I have let the tracejob to access the torque server logs, gc3pie starts
working without any changes.
In case gc3ie runs on batch server machine that would be not an issue, however
this is not always the case, like mine.
It would be good to mention about this somewhere in doc( i could not find) or I
would keep the changes you have done so that the tracejob
command gets a job status even if only a job accounting info files are
available.
I'm open to both solutions for GC3Pie 2.5. What do you think would be
best, i.e., make GC3Pie work across the wider variety of TORQUE/PBS
configurations?
Not relying on tracejob working is the way forward imho...
regards,
Kenneth
