Last modified: 2014-10-22 08:54:55 UTC
jobs with wildcard release resource parameters are not interpret correctly if i am using jsub instead of qsub My testfile foo.sh: #$ -l release='*' #$ -w v echo "1" $qsub foo.sh verification: found suitable queue(s) $jsub foo.sh Unable to run job: Job 4945440 (-l h_vmem=262144k,release='*') cannot run at host "tools-exec-15.eqiad.wmflabs" because it offers only hf:release=precise Job 4945440 (-l h_vmem=262144k,release='*') cannot run at host "tools-exec-12.eqiad.wmflabs" because it offers only hf:release=trusty ... verification: no suitable queues. The same result happens if you add the resource as command line argument (jsub -l resource='*'), but this is more complicated for debugging because you cannot add "-w v".
I found a solution: wildcard still does not work with jsub, but regex -l release=trusty|precise (without quoting) at script header solves my problem. qsub also accepts single or double quotes, but not jsub. It is still confusing that resource values are interpreted differently by jsub and qsub. But i am closing this bug because my problem is solved.
