+
Skip to content

Conversation

jfy133
Copy link
Member

@jfy133 jfy133 commented Aug 22, 2025

Thanks to @mahesh-panchal for the fix!

Close #632

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 pipelines 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).

Copy link

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!

@jfy133 jfy133 changed the base branch from master to dev August 22, 2025 07:13
Copy link

github-actions bot commented Aug 22, 2025

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

Posted for pipeline commit eaa4a65

+| ✅ 291 tests passed       |+
!| ❗  19 tests had warnings |!

❗ Test warnings:

✅ Tests passed:

Run details

  • nf-core/tools version 3.3.2
  • Run at 2025-08-22 07:17:05

Copy link
Member

@erikrikarddaniel erikrikarddaniel left a comment

Choose a reason for hiding this comment

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

Looks all good, although, IIRC, I had to do the Math.floor() and Math.max() things in bbmap/align to make sure I got an integer rounded down and that I never got a 0.

@mahesh-panchal
Copy link
Member

@erikrikarddaniel
Copy link
Member

erikrikarddaniel commented Aug 22, 2025

Correct. I'm mixing up the modules. The one I meant is bbmap/bbnorm: https://github.com/nf-core/modules/blob/48ca3de1737b0144aa9fe05bea2b681f0ae45a95/modules/nf-core/bbmap/bbnorm/main.nf#L28-L42

And, again, the Math.round() must be redundant.

@jfy133 jfy133 merged commit 9e18b4d into dev Aug 22, 2025
9 checks passed
@jfy133 jfy133 deleted the update-bbduk-memory branch August 22, 2025 07:48
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.

Process BBMAP_BBDUK uses float values on maxmem resulting in JVM error

3 participants

点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载