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

--changed-since and a path to test file conflict #272

Open
edmundmiller opened this issue Nov 18, 2024 · 1 comment
Open

--changed-since and a path to test file conflict #272

edmundmiller opened this issue Nov 18, 2024 · 1 comment

Comments

@edmundmiller
Copy link
Contributor

When running with both for example

nf-test test --changed-since HEAD^ path/to/main.nf.test

The changed-since takes presidence and the tests in the test file are ignored.

I'd like to be able to run the command and only the tests in the test file be considered.

But this may be difficult to implement and we should just use a tag.

edmundmiller added a commit to nf-core/modules that referenced this issue Nov 18, 2024
edmundmiller added a commit to nf-core/modules that referenced this issue Nov 18, 2024
edmundmiller added a commit to nf-core/modules that referenced this issue Nov 18, 2024
* ci: Attempt to split everything out

Don't hate me Adam

* 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

Idk what we're going to do about these...

* 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

https://nfcore.slack.com/archives/CJRH30T6V/p1724406283145319

* test: Snapshot the versions contents, not the hash

#6505

* ci: Keep running nf-core lint the way it was

Blocked by nf-core/tools#3140

* ci: Move conda skips out

* ci: Address a comment

* style: Move prettier and editorconfig to pre-commit

#4554 (comment)

* ci: Add note about nf-core lint pre-commit

* chore: Copy over conda skips

a004c86
2da71b7

* ci: only-changed => changed-since

* Add confirm-pass

* ci: dynamically set shards

* ci: Run 3 process jobs per CI run as an example

* install nf-test

* fix install nf-test

* fix install nf-test

* ci: Remove dynamic number of shards, and combine process and workflow filters

* ci: Remove variable Nextflow versions

* test: Update bowtie versions

* ci: Fix indention

* ci: We're not testing multiple python versions

* style: Clean up job names

* build: Remove invisible characters?

* test(bowtie): Bump snapshots

* style: Remove stray comment

* ci: Add GPU tests in their own workflows

These will only get trigger on the paths listed

* ci(gpu): Clean up triggers and make a note about

how to make the includes smarter

* ci: pip install cryptography

* ci: Try removing path

* ci: Add fetch-depth and remove duplicate checkout

* test: Remove the second gpu profile

* ci: Add path back in

* ci(gpu): Remove changed-since

* ci: Fix missed dorny/paths-filter update

Co-authored-by: mashehu <[email protected]>

* Add changes from codereview

Co-authored-by: mashehu <[email protected]>

* style: Remove example TODO comments

https://github.com/nf-core/modules/pull/6286/files#r1846856369
Co-authored-by: mashehu <[email protected]>

* refactor: Try tags for GPU CI

askimed/nf-test#272

* style: Set NFT_WORKDIR as an ENV variable

* style: Run lsp format on a parabricks module

For science

* test: Add gpu tags to parabricks

* ci: Split tags out of matrix

* Revert "style: Run lsp format on a parabricks module"

This reverts commit d134e78.

* ci: Fix name

---------

Co-authored-by: Edmund Miller <[email protected]>
Co-authored-by: maxulysse <[email protected]>
Co-authored-by: mashehu <[email protected]>
@lukfor
Copy link
Collaborator

lukfor commented Dec 3, 2024

Thanks, I will take a look to see how complicated this would be 👍

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

No branches or pull requests

2 participants