Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

torque script PBS directive error #62

Closed
ircwaves opened this issue Nov 29, 2016 · 4 comments
Closed

torque script PBS directive error #62

ircwaves opened this issue Nov 29, 2016 · 4 comments
Assignees
Labels

Comments

@ircwaves
Copy link

Interesting project. In doing a quick test-drive, I've hit a PBS directive error. It might be a config error or even a torque version mismatch, but fyrd.get_cluster_environment() does return 'torque'. mem gets the complaint, but I believe walltime also needs to be prefixed by -l in the job script.

>>> j = fyrd.Job('ls ', ['.'])
>>> j.submit()
20161129 17:28:48.344 | WARNING --> Command qsub /home/icooke/ls.0.1493c48f.cluster.qsub failed with code 1, retrying.
20161129 17:28:49.348 | WARNING --> Command qsub /home/icooke/ls.0.1493c48f.cluster.qsub failed with code 1, retrying.
20161129 17:28:50.352 | WARNING --> Command qsub /home/icooke/ls.0.1493c48f.cluster.qsub failed with code 1, retrying.
20161129 17:28:51.359 | WARNING --> Command qsub /home/icooke/ls.0.1493c48f.cluster.qsub failed with code 1, retrying.
20161129 17:28:52.364 | CRITICAL --> qsub failed with code 1
-----------------------------------> stdout: 
-----------------------------------> stderr: qsub: directive error: mem=4000MB

And the script file

$ cat /home/icooke/ls.0.1493c48f.cluster.qsub
#!/bin/bash
#PBS -l nodes=1:ppn=1
#PBS mem=4000MB
#PBS -q myqueue
#PBS -e /home/icooke/ls.0.1493c48f.cluster.err
#PBS -o /home/icooke/ls.0.1493c48f.cluster.out
#PBS walltime=04:00:00
mkdir -p $LOCAL_SCRATCH > /dev/null 2>/dev/null
cd /home/icooke
date +'%y-%m-%d-%H:%M:%S'
echo "Running ls.0.1493c48f"
ls .
exitcode=$?
echo Done
date +'%y-%m-%d-%H:%M:%S'
if [[ $exitcode != 0 ]]; then
    echo Exited with code: $exitcode >&2
fi

@MikeDacre MikeDacre added the bug label Dec 1, 2016
@MikeDacre MikeDacre self-assigned this Dec 1, 2016
@MikeDacre
Copy link
Owner

Thank you @ircwaves, that is definitely a bug, I am surprised I missed something so obvious. Fixing it now.

@MikeDacre
Copy link
Owner

OK, fixed in dev, now, I will merge it into master tomorrow once all the tests pass.

@ircwaves
Copy link
Author

ircwaves commented Dec 1, 2016

Muy bueno. Good luck with everything on your road to the cheeseshop.

@MikeDacre
Copy link
Owner

Now fixed in master also, I will release another beta next week and it will be included there. Thanks again @ircwaves.

@MikeDacre MikeDacre moved this from Bugs to Done in Initial Stable Version Aug 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants