1673
100%

Ran 03 Apr 2016 08:17AM UTC

Jobs 1

Files 64

Run time 2s

Badge

Embed ▾

pending completion

Build # 1673

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

4454 of 4699 relevant lines covered (94.79%)

0.95 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	1673.1 (TERM=dumb)	03 Apr 2016 08:17AM UTC	0	94.79	Travis Job 1673.1

Source Files on build 1673

Detailed source file information is not available for this build.

ben-manes / caffeine / 1673
100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 1673

ben-manes / caffeine / 1673 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 1673

ben-manes / caffeine / 1673
100%

README BADGES
x