-
Notifications
You must be signed in to change notification settings - Fork 192
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
Modules: Have component_files_identical check for new optional files in modules #2816
base: dev
Are you sure you want to change the base?
Conversation
Co-authored-by: Matthias Hörtenhuber <[email protected]>
Co-authored-by: Matthias Hörtenhuber <[email protected]>
Co-authored-by: Matthias Hörtenhuber <[email protected]>
Co-authored-by: Matthias Hörtenhuber <[email protected]>
@nf-core-bot changelog |
Hello! What I modified with the last commit is using all files from the modules repo to check if the component files are identical, so we don't need to take into worry about file names in case we have modules with special cases. The tests were failing because one file from the modules repo didn't exist in the pipeline, which should be considered as |
@mirpedrol : Thanks, Juliá. Concerning the failing test: It seems to me that the reason it is failing is that the file |
Checking a bit further on the remaining failing test. We are only installing the module to a pipeline and linting, so it should pass. When I try reproducing this locally, the |
I see. This would have been easy to debug if the test had printed the content of |
Co-authored-by: Matthias Hörtenhuber <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files☔ View full report in Codecov by Sentry. |
@nf-core-bot changelog |
@nf-core-bot changelog |
#2774
PR checklist
CHANGELOG.md
is updateddocs
is updated