You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TST: Skip tests that use a large amount of memory by default (#31007)
* TST: Reduce memory usage of test_downsample_interpolation_stage
By cutting the grid by one-tenth in each dimension, this cuts memory
usage from 1.0GiB to 65.2MiB. I temporarily added an assert in
`_ImageBase._make_image` to confirm that the interpolation stage did
correctly switch to 'rgba' as well.
* TST: Delete test_invisible_Line_rendering
This test tries to check for slowdowns, which is inherently flaky (as
noted by the comment), and we don't check `set_visible` for other
artists.
* TST: Skip tests that use a large amount of memory by default
According to memray, these tests use fairly large amounts of memory:
- lib/matplotlib/tests/test_simplification.py::test_throw_rendering_complexity_exceeded: 2.2GiB
- lib/matplotlib/tests/test_agg.py::test_chunksize_fails: 2.0GiB
- lib/matplotlib/tests/test_image.py::test_large_image[png-col-16777216-2\\*\\*24 rows-upper]: 1.0GiB
- lib/matplotlib/tests/test_image.py::test_large_image[png-col-16777216-2\\*\\*24 rows-lower]: 1.0GiB
- lib/matplotlib/tests/test_image.py::test_large_image[png-row-8388608-2\\*\\*23 columns-lower]: 537.8MiB
- lib/matplotlib/tests/test_image.py::test_large_image[png-row-8388608-2\\*\\*23 columns-upper]: 537.8MiB
The next closest tests use just 216MiB, then 145.5MiB, etc. and then the
majority under 100MiB.
If you're unlucky, with 4-way xdist you might use upwards of 6GiB RAM if
you get all these on separate processes.
The above tests are all fairly low-level checks for Agg renderer limits
that are not likely to change often, so skip them by default unless on
CI.
0 commit comments