dpnp
dpnp copied to clipboard
Handling warnings in pytest
This PR suggests getting rid of use -p warnings flag in pytest configuration and handling warnings separately.
This will help to see new warnings during development
- [X] Have you provided a meaningful PR description?
- [ ] Have you added a test, reproducer or referred to issue with a reproducer?
- [ ] Have you tested your changes locally for CPU and GPU devices?
- [ ] Have you made sure that new changes do not introduce compiler warnings?
- [ ] Have you checked performance impact of proposed changes?
- [ ] If this PR is a work in progress, are you filing the PR as a draft?
View rendered docs @ https://intelpython.github.io/dpnp/index.html
There are still warnings on PVC:
=========================================================================================== warnings summary ===========================================================================================
tests/test_sycl_queue.py::test_from_dlpack_with_dpt[complex64-level_zero:gpu:0]
tests/test_sycl_queue.py::test_from_dlpack_with_dpt[complex64-level_zero:gpu:1]
/home/gta/miniconda3/envs/dpnp_dev/lib/python3.10/site-packages/numpy/testing/_private/utils.py:722: RuntimeWarning: invalid value encountered in equal
func=lambda xy: xy == +inf,
tests/test_sycl_queue.py::test_from_dlpack_with_dpt[complex64-level_zero:gpu:0]
tests/test_sycl_queue.py::test_from_dlpack_with_dpt[complex64-level_zero:gpu:1]
/home/gta/miniconda3/envs/dpnp_dev/lib/python3.10/site-packages/numpy/testing/_private/utils.py:725: RuntimeWarning: invalid value encountered in equal
func=lambda xy: xy == -inf,