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

Use resource limits instead of setting process directives in nf-test configuration #3066

Open
adamrtalbot opened this issue Jul 15, 2024 · 0 comments

Comments

@adamrtalbot
Copy link
Contributor

adamrtalbot commented Jul 15, 2024

Description of feature

Similar to #3037, we should set the maximum cpu, memory and time limit on nf-tests. This can be mostly done by the -profile test however it is beneficial to set a hard limit when using nf-tests so accidentally not using the test profile does not cause issues.

See https://github.com/nf-core/rnaseq/blob/99fb7efc9d2b17a7940f745570ff162c04548bc4/tests/nextflow.config#L23-L30 for current implementation in tests/nextflow.config:

// Impose sensible resource limits for testing
process {
    withName: '.*' {
        cpus   = 2
        memory = 3.GB
        time   = 2.h
    }
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant