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

Allow custom process.time #52

Closed
ning-y opened this issue Feb 18, 2024 · 0 comments · Fixed by #53
Closed

Allow custom process.time #52

ning-y opened this issue Feb 18, 2024 · 0 comments · Fixed by #53

Comments

@ning-y
Copy link
Contributor

ning-y commented Feb 18, 2024

Some doLastzClusterRun jobs exceed the hardcoded process.time of two days.

JOB_TIME_REQ = '48h'

The default behavior for these jobs seems to be to rerun. However, the result appears to be an infinitely rerunning failing job. (Maybe there is an upper limit to the number of reruns, but for two day--long jobs I haven't seen this reach an upper limit).

An easy solution is to allow customizable JOB_TIME_REQ by setting 48h as the default and allowing user overrides by command line option.

I suppose it is also possible to split the genomes into smaller chunks, but I do not know enough about genome-genome alignments to say if that might affect the resulting alignments. If it might affect alignment results, I would prefer increasing JOB_TIME_REQ.

This issue is related to #43 and perhaps #48.

Personally, a very long JOB_TIME_REQ is fine for me, since I run the Nextflow process with local executor within a single large cluster job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant