2
100%
master: 100%

Ran 09 Mar 2017 07:50AM UTC

Files 4

Run time 0s

Badge

Embed ▾

Committed 09 Mar 2017 07:46AM UTC coverage: 100.0%. Remained the same

Job # PYVER="3.5"

Build Type

Pull #11

travis-ci

Committed by

web-flow

Commit Message

Use NumPy 32-bit int in `tinfo` doctest.

Appears that on Windows `int` means 32-bit int even when a 64-bit build
of Python was made. So instead of relying on `int` generally, which will
vary between 64-bit or 32-bit for Unix or Windows respectively, specify
the number of bits with a NumPy type. Also as there is a chance of
representation subtleties between Unix and Windows with a 64-bit int
(e.g. `L` postfix) chose a type that is least likely to run into these
issues in the doctest. In particular, switch to a 32-bit int from NumPy.
This both specifies a specific type of integer and picks one where its
max and min values will fall within what a 32-bit int can represent.

Pull Request Pull Request #11: Use NumPy 32-bit int in `tinfo` doctest

Run Details

58 of 58 relevant lines covered (100.0%)

1.0 hits per line

Source Files on job 84.2 (PYVER="3.5")

Coverage	∆	File	Lines	Relevant	Covered	Missed	Hits/Line

jakirkham / npctypes / 84 / 2
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 84.2 (PYVER="3.5")

jakirkham / npctypes / 84 / 2 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 84.2 (PYVER="3.5")

jakirkham / npctypes / 84 / 2
100%
master: 100%

README BADGES
x