-
Notifications
You must be signed in to change notification settings - Fork 5
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
Update to the deault github runner #186
Conversation
change to the default runner for now.
|
@yumisims @DLBPointon There is java process asking for 36G memory directly. Can we try |
Hi Guoying, sorry for taking my time getting back to you. I've been on holiday.
The process was in there. However, it was coded to not run on the GitHub runner due to the sheer amount of resources the process needs. I thought the runner was to still get the tiny test working properly and then a large run on the farm. If not then I can add the full test back in, but Tiny will also need the custom runner.
We can indeed try this. |
@DLBPointon need Will @weaglesBio to update the juicer part first. then we could minimize the heap, I am thinking to optimise the other resource a bit, these should resolve the testing problem. |
Sure ok. I'll get some decent graphs going. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rapid testing passed, we will open another branch to carry out full test. Thanks @gq1 @DLBPointon @muffato
change to the default runner for now.
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).