[do not merge] stress testing PR #6286

[adamrtalbot]

• ci: Attempt to split everything out
• ci: Add changed since, sharding, and ci
• ci: Add filter to try to get jobs split up
• ci: Switch to only-changed
• ci: See if follow-dependencies works without "related-tests"
• ci: Remove skipped tests
• ci: Actually use the nf-test version
• ci: module => process
• ci: Clean up job names
• dummy: Make a change
• ci: Skip test.tap
• ci: Add fetch-depth
• ci: Clean up name
• ci: Lint everything
• ci: Get the job names clean
• ci: Add hide-progress on linting
• ci: Add psuedocode for conda-fail.yml
• test: Snapshot the versions contents, not the hash
• ci: Keep running nf-core lint the way it was
• ci: Move conda skips out
• ci: Address a comment
• style: Move prettier and editorconfig to pre-commit
• ci: Add note about nf-core lint pre-commit
• chore: Copy over conda skips
• fake change to UNTAR

[edmundmiller]

Here we go! https://github.com/nf-core/modules/actions/runs/11113847492?pr=6716

That only ran the associated tests. Got another commit that changes the actual module.

[edmundmiller]

Okay @adamrtalbot I'm considering that properly stressed, but feel free to keep going if you want!

[edmundmiller]

Looks like it made it through about 25 tests on a runner? I wonder if we can clean up after each test.

[adamrtalbot]

Let's do a proper stress test: https://github.com/nf-core/modules/pull/6716/commits/c9f1ed02f9603f666e5d2571b0b5bcc1d5961c0f

[adamrtalbot]

Yeah ~30 is the limit. There will be some weird exceptions where people insist on downloading a giant database but in some ways I'd like this to fail.

So how do we batch up to 25 tests without using a dynamic matrix again?