4
57%
develop: 62%

Ran 01 May 2016 11:09PM UTC

Files 90

Run time 3s

Badge

Embed ▾

Committed 01 May 2016 10:54PM UTC coverage: 57.283% (+0.4%) from 56.918%

Job # TOXENV=py34

Build Type

push

travis-ci

Committed by

flacjacket

Commit Message

Fix odd Python 3.5 test issue

When the "thisisatotallynonexistantpathforsure" completer would run, the
_next_ test would fail in a nasty way, sometime exiting with return code
-11, and other times exiting with return code -6 and dumping "Fatal
Python error: GC object already tracked".  I have not reproduced this
locally on my instance of 3.5, nor does it fail with 3.6alpha, so it may
be particular to 3.5.0.  These chages seem to fix this behavior without
changing the functionality.

Run Details

6123 of 10689 relevant lines covered (57.28%)

0.57 hits per line

flacjacket / qtile / 650 / 4
57%
develop: 62%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 650.4 (TOXENV=py34)

flacjacket / qtile / 650 / 4 57% develop: 62%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 650.4 (TOXENV=py34)

flacjacket / qtile / 650 / 4
57%
develop: 62%

README BADGES
x