How to find jobscripts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
/data/rc/jobscript_archive/<user>/<YYYYMMDD>/<jobid>.savescript
This is useful for RC staff to resolve devops issues and for facilitation problem solving.
We need this documented in the rc-how-to gitlab repo, and in the rc internal docs. (And maybe those could be merged...?).
It is also useful for researchers to review and to resolve their own issues.
To find a job script either of the following can work
- Having the
jobidand usingfind. - Having the datetime and using
sacct -S ... -E ...to find thejobid. If there are many jobs, then having a unique-ishjobnamecan help narrow down the selection.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue's job-script archive path and the two lookup approaches: find by jobid, or sacct -S ... -E ... with an optional jobname. Document these instructions in the rc-how-to GitLab repo and the RC internal docs; done means both documentation locations explain how staff and researchers can find a job script.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100