1
94%
master: 92%

Ran 01 Jul 2015 08:11PM UTC

Files 159

Run time 7s

Badge

Embed ▾

Committed 01 Jul 2015 07:57PM UTC coverage: 95.767% (-0.7%) from 96.438%

Job # 365.1

Build Type

push

travis-ci

Committed by

mp911de

Commit Message

Retry commands that have an inactive channel after execution. Possible reason for #81

This is tricky because, the write could failed and we do not know, whether the write was sucessful or not. Was the command written? Was it flushed already? When did it happen and did the remote process it already?
With listening (getting an exception) or without we do not know, when an error occurred, therefore we retry it. On the next try, the command is either queued or sent and this way retried. No commands get lost.

Coverage Stats

5362 of 5599 relevant lines covered (95.77%)

0.96 hits per line

mp911de / lettuce / 365 / 1
94%
master: 92%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 365.1

mp911de / lettuce / 365 / 1 94% master: 92%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 365.1

mp911de / lettuce / 365 / 1
94%
master: 92%

README BADGES
x