Fabien Viale
Fabien Viale
Because nearly all methods (killTask, getTaskResults) of the Scheduler API uses Task Names as keys. It makes sense, the user doesn't know taskids (they are not returned when a job...
The only requirement is that your task name be unique for a given job. You can reuse the same task across different jobs if you want to. The Task Names...
Unfortunately, not yet.
An issue with a similar error message has been reported a few days ago : #2468 using the RunAsMe mode But the scenario you describe seems different and it's _very_...
Add documentation.
yes it's still valid.
Actually, starting from release 7.28, we have also the exit code, if the main script execution is a bash task. Here is an example of the variables printed in the...
Errata: actually the clean script contains all these bindings since many releases, it's only in case of a walltime that the bindings were not propagated before release 7.28
Maybe it's possible to improve the performance by playing with the VFS cache. Ideally, suppose that we have a way to recursively compute all meta data for a given remote...
I didn't think of that, I was suggesting to change the cache strategy on the fly inside the task to reduce remote calls. By default, a remote call occurs at...