-
Notifications
You must be signed in to change notification settings - Fork 417
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
Light refactoring #1422
Light refactoring #1422
Conversation
|
So far this PR seems like it is adding some stuff and not refactoring 😄 Anyways, linter says "Param modules_testdata_base_path from nextflow config not found in nextflow_schema.json" |
sorry, this is an ongoing PR, I should have put it as a draft |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm 🚀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM too
1bf5222
sorry still need to fix |
…ath(params.fasta_fai)
There's a nf-core linting failure that needs to be addressed before review:
|
In 4575cba, then full-test is still not running on awsbatch :-/ I still get:
(The full-tests also fails no the dev-branch, but due to other bugs which have now been fixed in this PR.) The "small" test-profile also fail on 4575cba with a similar error but from another process:
Seemingly similar issue reported here, but the fix proposed by @bentsherman didn't solve it. clue: The "small" test-profile can run with awsbatch on the dev-branch (at least in one mamba-env), which seem to indicate that it is something in this PR that is causing the problem with awsbatch. |
@asp8200 Could the problem maybe be happening when we try to assign a tag to the job? Maybe AWS batch only supports tags of a certain length, or the files for the AWS Batch dataset are too long / contain illegal characters. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why stuff is being moved around, but if it works and isn't more confusing than before, then OK. By the way, the error reported from the linter can be ignored. It is a know bug in the linter.
The test and test_full now pass locally. (But not over awsbatch. However, we now know what the problem with that is, and we have at least one possible fix.)
@maxulysse What still remains to be done on this PR? This is a pretty substantial bit of refactoring, and I think it would be good to get this merged back into dev sooner rather than later. Also, as general practice for nf-core development, is it acceptable for major rewrites like this one to merge a mostly correct set of changes into dev and then address the remaining failures as PRs to that branch? |
I agree with you @kenibrewer, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. However, we still need to fix the runOptions/containerOptions-issue so that the pipeline can run over awsbatch. We do have a fix for that but it isn't great:
yeah, but that's another issue |
The linter is failing, but that is a bug in the linter which has been solved in the dev-version of the tool.
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).