Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/4232
Thanks! ð
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/4232
Thanks for the fixups @aljoscha :-D
The last Travis run was successful, the test name rename should not affect
anything.
Merging this ..
---
If your project is set up for it, you can reply
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/4232
Ah scratch that, perhaps the `CheckpointSettingsSerializableTest` is
sufficient.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/4232
Thanks for the quick fix @aljoscha!
Regarding tests:
Can we also have another test that verifies `JobGraphs` containing custom
`StateBackend`s or `StateBackends` with custom classes can
