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
We intentionally raise DeprecationWarnings/FutureWarnings as errors in pytest, such that we're always notified when something will demand a change on our end. This works fine for warnings being thrown at the parent pytest process, but apparently the same doesn't happen for LocalCluster and children classes.
Running that will cause the warning in the pytest parent process to be raised as error, as we expect, but both sync and async versions of LocalCluster will raise FutureWarnings without any being raised as errors, see below.
I don't know if there's anything we can do in pytest so that it will capture warnings in subprocesses as well, but that would be the case we truly want to test.
The text was updated successfully, but these errors were encountered:
We intentionally raise
DeprecationWarning
s/FutureWarning
s as errors inpytest
, such that we're always notified when something will demand a change on our end. This works fine for warnings being thrown at the parentpytest
process, but apparently the same doesn't happen forLocalCluster
and children classes.dask_cuda/tests/test_warning.py
Running that will cause the warning in the
pytest
parent process to be raised as error, as we expect, but both sync and async versions ofLocalCluster
will raiseFutureWarning
s without any being raised as errors, see below.output
I don't know if there's anything we can do in
pytest
so that it will capture warnings in subprocesses as well, but that would be the case we truly want to test.The text was updated successfully, but these errors were encountered: