2020-10-25 11:40:30 UTC - Lari Hotari: InactiveTopicDeleteTest and TopicDuplicationTest are also failing very often. The logs show 500 server error happening for TopicDuplicationTest, so it might be an actual problem and not just a flaky tests. In InactiveTopicDeleteTest, I can see the usage of Thread.sleep in the test and that's most likely the source of flakiness. Switching to use Awaitility (<http://www.awaitility.org/>) to replace Thread.sleeps in tests would be a great improvement. @Devin G. Bost’s PR <https://github.com/apache/pulsar/pull/6202> includes the usage of Awaitility to reduce test flakiness. I hope we get those improves included asap. ---- 2020-10-25 17:40:44 UTC - Jonas Dahl: @Jonas Dahl has joined the channel ---- 2020-10-26 06:43:48 UTC - Anup Ghatage: I noticed that Pulsar doesn’t have BouncyCastle FIPS switched on by default but the documentation leaves it up to the implementers to choose. Is there any specific reason for this? I thought BC-FIPS comes with the usual BouncyCastle stuff + FIPS compliance (which would be a good thing) right? ---- 2020-10-26 07:33:08 UTC - Lari Hotari: Another example where it took 7 attempts to get a test pass for a PR: <https://github.com/apache/pulsar/pull/8358> . The Pulsar CI is in pretty bad state. I hope others join the effort to get this problem solved asap. Is anyone else feeling the same pain? ---- 2020-10-26 08:37:13 UTC - Sijie Guo: @jia zhai would have a better answer for it. ---- 2020-10-26 08:38:13 UTC - Sijie Guo: Thanks @Lari Hotari for driving this. I’d recommend to pull the commonly failed tests in one of the github issues and break it up. +1 : Lari Hotari ----
