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

Centrifuge update to address mkfifo clashes #444

Merged
merged 6 commits into from
Feb 6, 2024
Merged

Conversation

jfy133
Copy link
Member

@jfy133 jfy133 commented Feb 3, 2024

Hopefully 🤞 fixes #422

PR checklist

  • This comment contains a description of changes (with reason).
  • If you've fixed a bug or added code that should be tested, add tests!
  • If you've added a new tool - have you followed the pipeline conventions in the contribution docs
  • If necessary, also make a PR on the nf-core/taxprofiler branch on the nf-core/test-datasets repository.
  • Make sure your code lints (nf-core lint).
  • Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
  • Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
  • Usage Documentation in docs/usage.md is updated.
  • Output Documentation in docs/output.md is updated.
  • CHANGELOG.md is updated.
  • README.md is updated (including new tool citations and authors/contributors).

@jfy133 jfy133 changed the base branch from master to dev February 3, 2024 14:53
Copy link

github-actions bot commented Feb 3, 2024

This PR is against the master branch ❌

  • Do not close this PR
  • Click Edit and change the base to dev
  • This CI test will remain failed until you push a new commit

Hi @jfy133,

It looks like this pull-request is has been made against the nf-core/taxprofiler master branch.
The master branch on nf-core repositories should always contain code from the latest release.
Because of this, PRs to master are only allowed if they come from the nf-core/taxprofiler dev branch.

You do not need to close this PR, you can change the target branch to dev by clicking the "Edit" button at the top of this page.
Note that even after this, the test will continue to show as failing until you push a new commit.

Thanks again for your contribution!

Copy link

github-actions bot commented Feb 3, 2024

nf-core lint overall result: Passed ✅

Posted for pipeline commit f9aee61

+| ✅ 195 tests passed       |+

✅ Tests passed:

Run details

  • nf-core/tools version 2.12.1
  • Run at 2024-02-05 16:03:54

CHANGELOG.md Outdated Show resolved Hide resolved
@LilyAnderssonLee
Copy link
Contributor

Super!!! Well done!!! I will test it now and will approve it once the job is completed.

@jfy133
Copy link
Member Author

jfy133 commented Feb 5, 2024

I hope it works 🤞

Copy link
Contributor

@LilyAnderssonLee LilyAnderssonLee left a comment

Choose a reason for hiding this comment

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

I don't have any issues regarding mkfifo, but instead, we don't get the correct *centrifuge.txt file. It seems that centrifuge-kreport didn't perform correctly. *.centrifuge.report.txt and *centrifuge.results.txt are correct.

Example of the file *centrifuge.txt

  0.52  42517   42517   U       0       unclassified
 99.48  8134168 8134168 -       1

CHANGELOG.md Outdated Show resolved Hide resolved
Co-authored-by: Lili Andersson-Li <64467552+LilyAnderssonLee@users.noreply.github.com>
@jfy133
Copy link
Member Author

jfy133 commented Feb 5, 2024

@sofstam I can't see your comment now, but yes I'm a bit concerned that the tests are failing :( need to investigate what that's meaning...

@sofstam
Copy link
Collaborator

sofstam commented Feb 5, 2024

@sofstam I can't see your comment now, but yes I'm a bit concerned that the tests are failing :( need to investigate what that's meaning...

I deleted it, I think Lili has an updated comment now.

@LilyAnderssonLee
Copy link
Contributor

@jfy133 Have you tested the new version of Centrifuge-kreport in standalone mode?

@jfy133
Copy link
Member Author

jfy133 commented Feb 5, 2024

No I didn't... my understanding from the release it wasn't meant to change...

https://github.com/DaehwanKimLab/centrifuge/releases/tag/v1.0.4.1

How does it look in your own test run/data?

@jfy133 jfy133 marked this pull request as draft February 5, 2024 10:33
@jfy133
Copy link
Member Author

jfy133 commented Feb 5, 2024

OK found the problem, it was a bug in my bioconda recipe (bad docs)... going to go back and update the recipe and the biocontainer and the moduel... 😅

@jfy133 jfy133 marked this pull request as ready for review February 5, 2024 19:43
@jfy133
Copy link
Member Author

jfy133 commented Feb 5, 2024

@LilyAnderssonLee final check?

Copy link
Contributor

@LilyAnderssonLee LilyAnderssonLee left a comment

Choose a reason for hiding this comment

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

The test run for my real data was finished successfully this time. Got all correct files!!!
LGTM!

@jfy133 jfy133 merged commit 1e414ef into dev Feb 6, 2024
24 checks passed
@jfy133 jfy133 deleted the centrifuge-update branch February 6, 2024 08:53
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.

Centrifuge error : (ERR): mkfifo(/tmp/72.inpipe1) failed.
3 participants