• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

jakirkham / xnumpy / 78 / 4
100%
master: 100%

Build:
Build:
LAST BUILD BRANCH: v0.1.3
DEFAULT BRANCH: master
Ran 09 Mar 2017 06:38PM UTC
Files 3
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

09 Mar 2017 06:35PM UTC coverage: 100.0%. Remained the same
PYVER="2.7"

push

travis-ci

jakirkham
Switch all doctest arrays from `int64` to `uint64`

It appears that on Windows the dtype will be displayed as part of the
NumPy array representation if it is `int32` on Python 3, but not Python
2. However, it will display the dtype as part of the NumPy array
representation on both Python 2 and 3 if it is `int64`. This contrasts
with Unix where a NumPy `int64` array does not have its dtype included
in the representation. To avoid this annoying issue, just pick a type
that will always show up in NumPy's array representation regardless of
OS or Python version. In particular, we pick `uint64`, which already
works for all of the arrays we have created. This way the doctests
should run without issues everywhere.

63 of 63 relevant lines covered (100.0%)

1.0 hits per line

Source Files on job 78.4 (PYVER="2.7")
  • Tree
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 78
  • Travis Job 78.4
  • 654a737f on github
  • Prev Job for PYVER="2.7" on fix_doctests_win (#75.4)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc