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
The distributed.comm.compression parameter is ignored, in RPC comms as well as when spilling to disk.
The problem is that it is read at import time in distributed.protocol.compression, which is loaded early on.
Try adding to the module, just before get_default_compression:
@gen_cluster(client=True, config={"distributed.comm.compression": "broken"})asyncdeftest_broken_compression(c, s, a, b):
x=c.submit(inc, 0)
awaitx# does not raise
Note how this test is particularly though as the worker runs in the same process, so there's no chance to reload the module. However, the situation does not improve when using Nannies.
As a result, the compression is hardcoded to:
lz4, if installed; otherwise
snappy, if installed; otherwise
no compression
Existing tests that change the compression from the default should be revised too. e.g. test_core.py::test_compression is setting the wrong config parameter so it's not testing anything useful.
This issue impedes unit tests that rely on some compression to be available (namely, test_scheduler.py::test_memory), since our 3.7/3.8 CI install neither lz4 nor snappy and @gen_cluster(client=True, config={"distributed.comm.compression": "zlib"}) won't work.
Activity