Reuti <[email protected]> writes: > Hi, > > while looking into another issue I stumbed over this: > > $ qsub -w e -l group=foo test.sh > Unable to run job: error: no suitable queues. > Exiting. > $ qsub -l group=foo test.sh > Your job 3393 ("test.sh") has been submitted > > Well, the implemented JSV will remove the invalid request (the complex > "group" is defined but not assigned to anything) and let the job run. If the > complex isn't defined at all, the error message is different: > > $ qsub -l bar=foo test.sh > Unable to run job: unknown resource "bar". > Exiting. > > Setting an invalid request in the JSV will also issue the above > "Unable to run job: error: no suitable queues." which is what I > expect. But should the SGE internal mechanism really be called before > the JSV has any chance to correct it? For now I think the SGE internal > check is done twice: one before and one after the JSV.
I've noted it to investigate. I've been meaning to implement just such tagging of job types for a while and didn't know there was that problem with doing it. _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
