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

swiftstack / container-crawler
88%
master: 89%

Build:
Build:
LAST BUILD BRANCH: 0.1.12
DEFAULT BRANCH: master
Repo Added 21 Dec 2018 10:12PM UTC
Files 5
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 feature/one-to-many-mappings
branch: feature/one-to-many-mappings
CHANGE BRANCH
x
Reset
  • feature/one-to-many-mappings
  • 0.1.10
  • 0.1.11
  • 0.1.12
  • 0.1.2
  • 0.1.3
  • 0.1.4
  • 0.1.5
  • 0.1.6
  • 0.1.6.1
  • 0.1.7
  • 0.1.8
  • 0.1.9
  • bug/call_close_if_possible
  • bug/fix-device-dir
  • bug/pre-sharding-swift
  • bug/prune-sharded-containers
  • bug/sharded-containers
  • bug/sharded-status-tracking
  • bug/sharding-exclude-extraneous-containers
  • feature/disable-mappings
  • feature/expose-more-container-stats
  • improvement/better-logs
  • improvement/clean-up-status
  • improvement/configurable-retry-count
  • improvement/expose-exception-type
  • improvement/log-tracebacks
  • improvement/pass-workers
  • improvement/release-resources
  • master
  • py3
  • stable_shard

pending completion
220

Pull #37

travis-ci-com

web-flow
Allow for one-to-many mappings.

Change the tracking of in-progress containers to not be keyed only off
the account/container, but take into account the full settings
dictionary. This change does not do anything to validate that the
numerous mappings make sense (e.g. they could be in conflict with each
other or overwrite data if the discrepancy is in how the data is
handled). That problem is outside the ContainerCrawler purview.
Pull Request #37: Allow for one-to-many mappings.

121 of 135 branches covered (89.63%)

Branch coverage included in aggregate %.

6 of 6 new or added lines in 1 file covered. (100.0%)

293 of 334 relevant lines covered (87.72%)

0.88 hits per line

Relevant lines Covered
Build:
Build:
334 RELEVANT LINES 293 COVERED LINES
0.88 HITS PER LINE
Source Files on feature/one-to-many-mappings
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
220 feature/one-to-many-mappings Allow for one-to-many mappings. Change the tracking of in-progress containers to not be keyed only off the account/container, but take into account the full settings dictionary. This change does not do anything to validate that the numerous mappi... Pull #37 10 Jun 2019 11:24PM UTC web-flow travis-ci-com pending completion  
219 feature/one-to-many-mappings Allow for one-to-many mappings. Change the tracking of in-progress containers to not be keyed only off the account/container, but take into account the full settings dictionary. This change does not do anything to validate that the numerous mappi... push 10 Jun 2019 11:22PM UTC timuralp travis-ci-com pending completion  
218 feature/one-to-many-mappings Allow for one-to-many mappings. Change the tracking of in-progress containers to not be keyed only off the account/container, but take into account the full settings dictionary. push 08 Jun 2019 01:24AM UTC timuralp travis-ci-com pending completion  
See All Builds (134)
  • 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