Skip to content

Conversation

@gburnett-nvidia
Copy link
Contributor

PR checklist

Closes #XXX

  • 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 module conventions in the contribution docs
  • If necessary, include test data in your PR.
  • Remove all TODO statements.
  • Emit the versions.yml file.
  • Follow the naming conventions.
  • Follow the parameters requirements.
  • Follow the input/output options guidelines.
  • Add a resource label
  • Use BioConda and BioContainers if possible to fulfil software requirements.
  • Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
    • For modules:
      • nf-core modules test <MODULE> --profile docker
      • nf-core modules test <MODULE> --profile singularity
      • nf-core modules test <MODULE> --profile conda
    • For subworkflows:
      • nf-core subworkflows test <SUBWORKFLOW> --profile docker
      • nf-core subworkflows test <SUBWORKFLOW> --profile singularity
      • nf-core subworkflows test <SUBWORKFLOW> --profile conda

nf-test-gpu:
runs-on: "runs-on=${{ github.run_id }}/family=g4dn.xlarge/image=ubuntu24-gpu-x64"
runs-on: "runs-on=${{ github.run_id }}/family=g4dn.8xlarge/image=ubuntu24-gpu-x64"
Copy link
Contributor

Choose a reason for hiding this comment

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

looks good to me its just this change where I am unsure

Copy link
Contributor Author

@gburnett-nvidia gburnett-nvidia Oct 14, 2025

Choose a reason for hiding this comment

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

Based on the other PR it looks like it's okay for me to change it back before merging. And we'll have some discussions elsewhere about if there's a better way we can do this in the future.

@gburnett-nvidia gburnett-nvidia added this pull request to the merge queue Oct 15, 2025
Merged via the queue into nf-core:master with commit 99856f9 Oct 15, 2025
26 of 30 checks passed
@gburnett-nvidia gburnett-nvidia deleted the parabricks_starfusion branch October 15, 2025 17:52
@famosab famosab mentioned this pull request Oct 17, 2025
4 tasks
vagkaratzas pushed a commit that referenced this pull request Oct 24, 2025
* Creating new module folder for starfusion, using fq2bam as a starting point

* resolving commit issue

* Updating files to reflect starfusion instead of fq2bam. Tests not passing.

* Parabricks is running but failing. Must be an issue with the input data.

* Creating new starfusion_build folder. Copied from starfusion.

* Changing to using starfusion/build as base for new parabricks starfusion model

* Decremented starfusion_build to 1.7 for Parabricks compatibility

* Tested and linted new starfusion model

* Removing GPU docker options from nextflow.config

* Adding support for Chimeric.out.junction output in rnafq2bam

* Updating language in README.md

* Adding version checking to snapshot assertion

* Adding out_dir to test assertions

* Removing stub fail test

* Cleaning up data outputs

* Removing unnecessary tags from starfusion nftest

* Cleaning up tags in starfusion_build nftest

* Added test for chimeric output in rnafq2bam

* Fixing issue with empty output (problem was with passing the chimeric.out.junction from rnafq2bam)

* Changing to starfusion test dataset to fix empty junction file

* Making Chimeric.out.junction output detection more generic

* Cleaning up rnafq2bam test assertions

* Changing starfusion to output fusions and abridged fusions (for parity with baseline starfusion module) and cleaning up test assertions

* Removing chimeric tests due to hanging issue with CI runners

* Reducing memory requirements

* Updating mem requiremnts

* ci: Try 12xl

* Brining back chimeric tests

* Increasing CI runner GPU size

* Updating chimeric.out.junction snapshot in rnafq2bam

* Upgrading memory from 15 GB to 100 GB to meet minimum recommended requirements

* Chimeric.out.junction snapshot is not stable, so moving to just check file name and not contents

* Moving module params out of the config and into the test file

* Updating test data paths

* Updating readme

* Adding version printing back to snapshot

* Adding version printing back to snapshot (more places)

* Cleaning up module args

* Removing compatible versions from module (since it does not work)

* Scaling down instance size to match minimum system requirements

* Updating stub test

* Updating module outputs

* Updating stub test

* Updating meta.yml to match new module outputs

* Adding rnafq2bam snapshot

* Updating rnafq2bam outputs to fix stub test

* Fixing starfusion stub tests

* Updating README to include notes on testing for starfusion module

* Updating README to reflect new large instance for testing starfusion

* Updating to 4.6

* Adjusting memory requirements for rnafq2bam and starfusion testing to match g4dn.2xlarge

* Reverting github ci runner instance

---------

Co-authored-by: Edmund Miller <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants