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

update CI and Changelog #433

Merged
merged 3 commits into from
Oct 22, 2024
Merged

update CI and Changelog #433

merged 3 commits into from
Oct 22, 2024

Conversation

sateeshperi
Copy link
Contributor

No description provided.

@sateeshperi sateeshperi requested a review from a team as a code owner October 22, 2024 03:43
@sateeshperi sateeshperi self-assigned this Oct 22, 2024
Copy link

github-actions bot commented Oct 22, 2024

nf-core pipelines lint overall result: Passed ✅ ⚠️

Posted for pipeline commit ad2b289

+| ✅ 198 tests passed       |+
#| ❔   4 tests were ignored |#
!| ❗   1 tests had warnings |!

❗ Test warnings:

❔ Tests ignored:

✅ Tests passed:

Run details

  • nf-core/tools version 3.0.2
  • Run at 2024-10-22 04:07:24

@@ -35,6 +35,7 @@ jobs:
- "24.04.2"
- "latest-everything"
shard: [1, 2, 3, 4, 5]
filter: [process, workflow]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The pipeline-level tests are not included?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah good catch! should be pipeline and workflow

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And process? I think the idea is to test everything?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think its gonna overload the CI runners with too many tests to run

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we have to bank on the fact that the modules were/are tested in the modules repo and the pipeline CI runs only pipeline and workflow tests

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you should bring this up in the #nf-test channel and we can discuss/vote there

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if there are local modules with tests? Moreover, the tests are only triggered for the changed modules.

If there are no local modules or functions with tests, let's skip process.

One more thing. If the nextflow.config changes or something from the assets directory changes, will the pipeline-level tests be triggered? I like the CI of nf-core/rnaseq which checks for these changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

plz bring this up in the nf-test channel and lets discuss there and get some consensus

@sateeshperi sateeshperi merged commit 25061bf into nf-core:dev Oct 22, 2024
11 checks passed
@GallVp
Copy link
Member

GallVp commented Oct 22, 2024

LGTM!

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 this pull request may close these issues.

2 participants