380
87%
master: 92%

Ran 16 Aug 2015 06:35PM UTC

Jobs 3

Files 13

Run time 26s

Badge

Embed ▾

pending completion

Build # 380

Build Type

push

travis-ci

Committed by Gabriel Wicke

Commit Message

Don't perform expensive no-cache instance tests

While doing some latency testing I noticed that the title Foobar was really
slow to load (500ms). I eventually traced this down to many thousands of
revision entries (possibly hundreds of thousands), which are caused by x-ample
tests forcing revision refreshes with no-cache.

Looking at the config, I found another x-ample that continuously re-renders
Foobar's HTML. This only avoided filling up revision storage as the content of
Foobar does not change much between renders, and we have implemented an
optimization that avoids storing unchanged revisions.

In both cases, there is really not much of a point in testing re-renders
separately for each instance. We have plenty of data on backend connections
that we can set alerts on. Having RESTBase alerts go off when the Action API
is in trouble is confusing, which is the last thing we need when things aren't
working so well.

Run Details

1343 of 1544 relevant lines covered (86.98%)

276.79 hits per line

Jobs

ID	Job ID	Ran	Coverage
1	380.1	16 Aug 2015 06:35PM UTC	86.98	Travis Job 380.1
2	380.2	16 Aug 2015 06:35PM UTC	86.98	Travis Job 380.2
3	380.3	16 Aug 2015 06:35PM UTC	86.98	Travis Job 380.3

Source Files on build 380

Detailed source file information is not available for this build.

gwicke / restbase / 380
87%
master: 92%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 380

gwicke / restbase / 380 87% master: 92%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 380

gwicke / restbase / 380
87%
master: 92%

README BADGES
x