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

Grokzen / redis-py-cluster / 433 / 10
87%
unstable: 86%

Build:
Build:
LAST BUILD BRANCH: feature/redis-py-3.0
DEFAULT BRANCH: unstable
Ran 03 Apr 2016 12:02PM UTC
Files 10
Run time 0s
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

03 Apr 2016 11:56AM UTC coverage: 86.399%. First build
HIREDIS=1 REDIS_VERSION=3.0

push

travis-ci

Grokzen
Rebuild how max connections is handled to be more similar to how redis-py works
 - max_connections_per_node is now a direct option in StrictRedisCluster and not part of kwargs option
 - pubsub connections is no longer tracked in seperate variables, now works same way ad redis-py handles pubsub connections
 - Counting and enforcing of max_connections and max_connections_per_node is no longer done with _in_use_connections
   but with the tracker of how many that has been created so far
 - Added threading test method 'test_pubsub_thread_publish' to more easily verify that hammering publish commands works as expected
   even in a threaded environment.

1010 of 1169 relevant lines covered (86.4%)

0.86 hits per line

Source Files on job 433.10 (HIREDIS=1 REDIS_VERSION=3.0)
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 433
  • Travis Job 433.10
  • 88a86d38 on github
  • Next Job for HIREDIS=1 REDIS_VERSION=3.0 on rework-connection-pool-connection-limits (#455.2)
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

© 2026 Coveralls, Inc