-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test memory_limit=None for CUDAWorker #946
Conversation
The errors seem to be from Tornado deprecations. Could you add |
I've added the relevant lines, I hope, but let's wonder why this failure appeared, whereas it wasn't there yesterday. This is a deprecation warning that appeared in tornado 6.2 (tornadoweb/tornado#3097), which was released yesterday. distributed added a pin for tornado<6.2, which is what is causing this problem, yesterday (dask/distributed#6668). I guess that hasn't filtered down to the nightlies, because the failing run installed tornado==6.2. |
it seems to me that the pin is not valid for conda nightlies. If create a new environment:
It picks:
In any case, if ignoring the warnings suffices for u, I wouldn't worry too much about it, as Dask will eventually resolve the problem and support |
In any case I went ahead and attempted to fix the conda package as well in dask/distributed#6675, so we may be able to remove the |
The warnings are emitted with stacklevel=2, which means that the module that filterwarnings sees is the module of the caller of the deprecated function.
Can't filter on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @wence- .
@gpucibot merge |
This introduces a test that was a TODO in #944