Thomas Moreau

I confirm that I reproduce this. It seems to be linked to the newest version of `cloudpickle` released yesterday as this error disappears when downgrading it to `1.4`. Maybe @pierreglaser...

It seems that `dispatch_table` was an instance level field before but this got changed in `cloudpickle>=1.5` (see [here](https://github.com/cloudpipe/cloudpickle/pull/368/files#diff-74d08d32266e9c3f0598295e4e4310ffL440)). So the fix is simply to copy the table before registering the...

This failure is unrelated as it is linked to bug in `cloudpickle` which should be fixed with cloudpipe/cloudpickle#212

Another of this kind: [here](https://ci.appveyor.com/project/tomMoral/loky/builds/19949942/job/lt7b1ea3wjwch96x)

@jtlz2 I am not sure what you are doing here? Is there a typo and the executor should be created during `mymodule` import or should it be in the `opencv_work2`,...

We could but when this appears in the test report, this is from the `MainThread`. Here we seems to have an issue on a lock which is not safe. I...

I see. That was something I wanted to do for a long time as this will also permits to improve debugging of deadlocks. So I think it would be a...

It would be interesting to benchmark the argument transfert speed too. _Edited the issue with subtasks_

~Another random failure, but different, it seems it is [a deadlock....](https://ci.appveyor.com/project/tomMoral/loky/builds/19949942/job/lt7b1ea3wjwch96x)~ this one is related to #175

The same failure occurred on [appveyor](https://ci.appveyor.com/project/tomMoral/loky/builds/19973031/job/p7786a2l8abje5o9). This seems to be the same as the previous ones. ``` tests/test_reusable_executor.py::TestExecutorDeadLock:: test_in_callback_submit_with_crash[func3-args3-TerminatedWorkerError-EXIT\(0\)] PASSED [ 65%] ERROR: InvocationError for command 'C:\\projects\\loky\\.tox\\py27\\Scripts\\py.test.EXE -vxl --timeout=50 --skip-high-memory'...