-
Notifications
You must be signed in to change notification settings - Fork 879
Bff #8653
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
base: master
Are you sure you want to change the base?
Bff #8653
Conversation
@nictru, I don't understand why I get this error:
|
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.
Looks good. Just a few minor remarks to consider.
@nictru, why are |
This was because the branch in your fork was not up-to-date with the main branch of the nf-core repo - as you can see it is fixed now, as the branch was updated |
@LuisHeinzlmeier your The same issue was already encountered and fixed in one of the other demultiplexing modules that reference the same data, as you can see here. Btw, thanks @itrujnara for the review @LuisHeinzlmeier, if you wonder what Igor means with Harshil alignment, you can read about it here |
@itrujnara , thanks for the review! I adopted the feedback. And, @nictru, thank you very much for the help! I can add the directory-url now as input and the test is running locally (snapshots are up to date). However only for docker I have an error. I think this error might arise from |
The error originates from the OS (it's a SIGKILL), so it is probably not a Seurat issue. It is more likely that the script OOMs or executes illegal instructions, but just from the CI output it's hard to tell which is the case. |
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.
I've found minor issues in the meta. Once they are resolved, I'll approve the PR so you can merge as soon as you fix the CI issues.
For testing purposes I increased the memory limit for all processes from 4GB to 6GB. It seems to work now, so this means that running the BFF tests in docker uses between 4 and 6 GB of memory, while singularity and conda stay below the 4GB limit. As increasing the memory limit is probably not allowed, we will have to revert this. However, we now know what the problem is and need to reduce the memory footprint of the tests |
This reverts commit 9ee94c7.
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.
Everything looks fine now. Feel free to merge once you fix the CI issues.
GenerateCellHashingCalls
hadge
pipelineCLUSTER
because the test data is probably too small