1
100%
master: 100%

Ran 03 Apr 2016 06:47AM UTC

Files 64

Run time 1s

Badge

Embed ▾

Committed 03 Apr 2016 05:53AM UTC coverage: 94.935% (+0.3%) from 94.655%

Job # TERM=dumb

Build Type

push

travis-ci

Committed by

ben-manes

Commit Message

Ensure exception in maintenance task is logged

ForkJoinPool's internal runnable wrapper rethrows the exception, while
ForkJoinTask makes it available for the consumer as a Future result.
Adding this in as a safety net to let users know an unexpected failure
occurred.

I don't recall why exceptions from performCleanup were allowed to
propogate to the caller. This has something to do with the CacheWriter.
An explicit catch and log still abides by the old behavior, as we were
relying on FJP to log for us with the raw runnable.

Need to revisit and understand if propogation still makes sense.

Coverage Stats

4461 of 4699 relevant lines covered (94.94%)

0.95 hits per line

ben-manes / caffeine / 1671 / 1
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1671.1 (TERM=dumb)

ben-manes / caffeine / 1671 / 1 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1671.1 (TERM=dumb)

ben-manes / caffeine / 1671 / 1
100%
master: 100%

README BADGES
x