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

vispy / vispy / 9579324589 / 3
75%
main: 75%

Build:
DEFAULT BRANCH: main
Ran 19 Jun 2024 09:22AM UTC
Files 344
Run time 7s
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

19 Jun 2024 09:10AM UTC coverage: 51.93% (-0.02%) from 51.949%
9579324589.3

push

github

web-flow
Set self._data_dtype in scale_and_set_data for CPU scaled textures (#2601)

I noticed this warning when running tests, and I think it traces back to
the change in this PR.

```
vispy/visuals/tests/test_colormap.py: 6 warnings
vispy/visuals/tests/test_image.py: 39 warnings
vispy/visuals/tests/test_scalable_textures.py: 4 warnings
  /Users/aandersoniii/src/vispy/vispy/gloo/texture.py:18: DeprecationWarning: finfo() dtype cannot be None. This behavior will raise an error in the future. (Deprecated in NumPy 1.25)
    info = np.finfo(dtype)
```

See https://github.com/vispy/vispy/pull/2350#discussion_r1638869690 for
some context.

I am partly guessing what this code meant to be doing, but here the
`_data_dtype` is set the first time `scale_and_set_data` is called.
@brisvag at your suggestion I am trying to think of a test that could
have caught this, but need to think about it a little more.

4031 of 10497 branches covered (38.4%)

16655 of 32072 relevant lines covered (51.93%)

0.52 hits per line

Source Files on job run-3 - 9579324589.3
  • Tree
  • List 0
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 9579324589
  • 634c99af on github
  • Prev Job for on main (#9549534102.1)
  • Next Job for on main (#9843693704.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