1
91%
master: 89%

Ran 29 Jul 2014 11:42AM UTC

Files 51

Run time 29s

Badge

Embed ▾

Committed 29 Jul 2014 11:35AM UTC coverage: 91.326% (+0.05%) from 91.28%

Job # SKIP_VIRUS_SCAN=1 SKIP_SPLINTER_TESTS=1 MONGO_REPLICA_SET=''

Build Type

push

travis-ci

Committed by

roc

Commit Message

Change the conditions for a data-set being out of date

- If it's never been updated, we can assume that it's in work. This can be subject to discussion, but my hunch is this is going to be the simplest way to maintain this
- Return full data-set status objects for both in-date and out-of-date data-sets. We can mod the status endpoint to always return both, or just one, or just the other, depending on need. Again, a hunch, but I feel we should be able to see how in-date something is as well as how out-of-date it is.
- Add `max-age-expected` to the status object

Run Details

1653 of 1810 relevant lines covered (91.33%)

0.91 hits per line

alphagov / backdrop / 1720 / 1
91%
master: 89%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1720.1 (SKIP_VIRUS_SCAN=1 SKIP_SPLINTER_TESTS=1 MONGO_REPLICA_SET='')

alphagov / backdrop / 1720 / 1 91% master: 89%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1720.1 (SKIP_VIRUS_SCAN=1 SKIP_SPLINTER_TESTS=1 MONGO_REPLICA_SET='')

alphagov / backdrop / 1720 / 1
91%
master: 89%

README BADGES
x