Raúl Gracia
@eolivelli @zhaohaidao @hangc0276 We have done another set of failure injection tests to narrow down the issue. These are the results: - Bookkeeper 4.14 server and Bookkeeper 4.14 client: Tests...
@zymap thanks a lot for your analysis. Yes, you are right, we are using 4.14.2 concretely, as the last commit we have from mainline is [](https://github.com/apache/bookkeeper/commit/fb15b07892ceaa0955756a4c0f34149e1a142e14). And we do not...
@dlg99 thanks Andrey. While this situation can indeed happen (specially inducing failure injection at the network level), my understanding is that that would happen to any version of Bookkeeper, right?...
FYI @zymap @eolivelli @dlg99 we have performed the same test again with Bookkeeper 4.14.3 client as suggested by @zymap, but we have not been able to reproduce the issue this...
Thanks a lot @dlg99, I can certainly review #3513. But after the latest experiments we did with Bookkeeper 4.14.3, which includes #2794, we couldn't reproduce the issue, so I'm not...
@claudiofahey due to issues we had in previous releases merging `develop` into `master`, we have changed the release approach and the current development branch is `dev`. We plan to delete...
@claudiofahey maybe the failure you are seeing are related to the sporadic failures we see in Pravega core repo related to tests involving Pravega standalone: https://github.com/pravega/pravega/issues/5864
@claudiofahey I tested the sample and it works. Also compiled with JDK11 and JDK8 and it also works (`./gradlew installDist`). But I also observed the failure in test `kill5of6Test`. Please,...
@claudiofahey tests passed for me. I had to upgrade the Scala version of Spark in the Hadoop sample, as build was broken by one of the previous PRs. But now...