treasure-data / perfectqueue

84%

master: 100%

LAST BUILD ON BRANCH remove-huge-task-dump

branch: remove-huge-task-dump

CHANGE BRANCH

x

Reset

• remove-huge-task-dump
• enable-covealls
• master
• avoid_table_metadata_lock_part1
• avoid_table_metadata_lock_part2
• disable-coveralls-outside-ci
• v0.8.44
• rspec3
• add-specs
• remove-sqlite-support
• keep-gziped-data-as-is
• v0.8.45
• retry-on-finish
• use-CONNECTION_ID
• remove-transaction
• suppress-warning
• use-DO-for-RELEASE_LOCK
• separate-delete-and-acquire-queries
• add-TaskMonitorHook-spec
• it-is-mysql2-ruby
• check-timeout-on-update-in-acquire
• add-a-test-for-long-waiting-queue
• v0.8.46
• force-index-for-acquire-query
• require-ahead-on-time
• v0.8.47
• stress
• stable-0.8.44
• ensure-kill-child
• randomize-initial-cleanup_interval_count
• use-timeout-for-44-compat
• dont-delete-finished-tasks-of-v0.8.46
• log-acquire-time
• v0.8.44.1
• delete-v0.8.44-finished-tasks
• parallel-acquire
• stress-test-tool
• fix-cleanup_interval_count
• run-48-delete-query-in-connect_locked
• v0.8.48
• revert-v0.8.44-migration-path
• remove-useless-created_at-check
• Sequel-UniqueConstraintViolation
• retry-connect
• fix-random-failure
• merge-v07
• remove-unused-code
• v0.8.49
• add-more-specs
• include-spec-dir-for-simplecov
• remove-cancel_request
• check-timeout-on-acquire
• get_rid_of_v07_client
• mysql-compress
• v0.9.0
• avoid-deadlock-and-unlock-earlier
• v0.9.1
• use-v08-strategy-if-with-resource-limit
• v0.9.2
• sleep-between-lock-retry
• v08
• v08-sleep-between-lock-retry
• v0.8.50
• stress-test-supports-multiple-queues
• retry-connect-v08
• v0.8.51
• initial-logger-support
• extend-rdb-connect-timeout
• v0.8.51_for_test
• relax-sequel
• relax-sequel-version
• v0.10.0
• explicitly-specify-services-mysql
• v0.8.52
• extract_max_retry_as_config
• v0.8.53
• rdb-sslmode-support
• v0.10.1
• enhance_logging
• v0.8.54

Build # 43

Build Type

push

travis-ci

Committed by tagomoris

Commit Message

Remove dump of task request:
* In real application, its too huge to read, and also danger to dump all data for task in logs

Run Details

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

1037 of 1236 relevant lines covered (83.9%)

37.97 hits per line