• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

broadinstitute / viral-core
66%
master: 66%

Build:
Build:
LAST BUILD BRANCH: ct-swiftseq-demux-integration
DEFAULT BRANCH: master
Repo Added 10 Sep 2019 08:19PM UTC
Files 24
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH v2.3.3
branch: v2.3.3
CHANGE BRANCH
x
Reset
  • v2.3.3
  • ct-add-fgbio
  • ct-add-ncbi-datasets
  • ct-add-read-filtering-cli-cmd
  • ct-align_and_fix_without_supplementary_alignments
  • ct-barcode-helper-ntc-counting
  • ct-barcode-i5-single-index-bugfix
  • ct-bugfix-idxstats-fns
  • ct-bugfix-minimap2_idxstats
  • ct-bump-baseimage
  • ct-bump-baseimage-0.2.3
  • ct-bump-pysam
  • ct-bump-pytest
  • ct-bump-python-version
  • ct-bump-viral-baseimage-0.2.4
  • ct-gh-actions-jvm-heap-decrease
  • ct-ghactions-update-ubuntu
  • ct-github-actions
  • ct-help-text-correction
  • ct-option-to-include-dup-reads-in-filtering
  • ct-set-default-threads
  • ct-swiftseq-demux-integration
  • ct-update-baseimage
  • ct-update-docker-base
  • ct-update-docker-mem-calc
  • ct-update-testing
  • ct-version-read-fix
  • docs
  • dp-dev
  • dp-docs
  • dp-fasta-handling
  • ll-add_swiftseq_demux
  • master
  • v2.2.0
  • v2.2.1
  • v2.2.3
  • v2.3.0
  • v2.3.1
  • v2.3.2
  • v2.3.4
  • v2.3.5
  • v2.3.6
  • v2.4.0
  • v2.4.1
  • v2.4.2
  • v2.4.3

23 Aug 2024 09:11PM UTC coverage: 65.588% (-0.3%) from 65.842%
10532428583

push

github

web-flow
in util.version.py::get_project_path(), consider calling modules (#109)

When derived modules (i.e. viral-classify) are symlinked into viral-core and their versions are read from a VERSION file, only the path to the viral-core version file was used. This changes that behavior, so outer members of the call stack are checked for the presence of VERSION files as well (and if found, the version is read from the first/outermost one found).

(i.e. when calling ./taxon-filter.py --version, with these changes, the version of viral-classify is correctly returned rather than the version of viral-core)

Since this relies on the presence of a VERSION file to find the current "project path", this will fall back to the old behavior if viral-core has a VERSION file and a derived module lacks such a file.

This does not change the behavior where a version file will not be created for a derived module when calling `./symlinked_derived_module.py --version`

2979 of 4542 relevant lines covered (65.59%)

0.66 hits per line

Relevant lines Covered
Build:
Build:
4542 RELEVANT LINES 2979 COVERED LINES
0.66 HITS PER LINE
Source Files on v2.3.3
  • List 22
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
10532428583 v2.3.3 in util.version.py::get_project_path(), consider calling modules (#109) When derived modules (i.e. viral-classify) are symlinked into viral-core and their versions are read from a VERSION file, only the path to the viral-core version file was use... push 23 Aug 2024 09:21PM UTC web-flow github
65.59
See All Builds (281)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc