cc @mitar @suquark

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/8312/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/8311/
Test FAILed.

jenkins, retest this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/8314/
Test FAILed.

It's strange that test/runtest.py::GlobalStateAPI::testFlushAPI often fails in various tests. I have seen this many times.

jenkins, retest this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/8317/
Test FAILed.

jenkins, retest this please

The error appears to be

Runner Thread raised error.
Traceback (most recent call last):
  File "/ray/python/ray/tune/function_runner.py", line 76, in run
    self._entrypoint(*self._entrypoint_args)
  File "/ray/python/ray/tune/examples/tune_mnist_keras.py", line 178, in <lambda>
    lambda cfg, rprtr: train_mnist(args, cfg, rprtr))
  File "/ray/python/ray/tune/examples/tune_mnist_keras.py", line 40, in train_mnist
    intra_op_parallelism_threads=args.threads,
AttributeError: 'Namespace' object has no attribute 'threads'

in docker run -e RAY_USE_XRAY=1 --rm --shm-size=10G --memory=10G 11071230bfdb184c984566048cec671cf536cfbd087806d50f8c4d92ebfdc1a1 python /ray/python/ray/tune/examples/tune_mnist_keras.py --smoke-test

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/8324/
Test FAILed.

odd; I guess somehow this causes cloudpickle to not capture the scope completely correctly?

BTW, I am guessing that eventually having also this fix in might saves us some trouble. We are slowly porting code to use typing and it seems with Python 3.6 there could be troubles. So, maybe Ray could update cloudpickle to version which is includes that PR. (But we have not yet had been blocked by this, but we encountered in the past and found some workarounds.)

@suquark Could you check why tests here are failing?