2020-10-26 12:59:16 UTC - jia zhai: @Sijie Guo @Anup Ghatage right, there is no specific reason for this. It seems be more related to the project building, we may need to config the profile to build different bc type. but this seems a little hard in maven:joy:. It would be helpful, if anyone would like to contribute to this feature. ---- 2020-10-26 16:31:57 UTC - Anup Ghatage: I’m thinking why not keep it on by default? There aren’t any API differences for the most part. That way Pulsar will be FIPS compliant all the time. ---- 2020-10-26 17:05:50 UTC - Devin G. Bost: @Lari Hotari The reason I didn't finish the work on the flaky tests is because I ran out of time, and something odd I noticed (if I remember correctly) is that the changes caused 2-3 tests to fail more consistently. That's an unfortunate consequence of trying to fix too many of these flaky tests in one PR.
I'm hoping to resume work on this in a few weeks. +1 : Lari Hotari ---- 2020-10-26 17:06:55 UTC - Devin G. Bost: Thanks for the feedback. I'll take a look at this one specifically. +1 : Lari Hotari ---- 2020-10-26 17:14:07 UTC - Lari Hotari: @Devin G. Bost You have already done a great effort on that PR. Are you ok if some of the changes in your PR get reused in smaller PRs asap? I believe it would be fair to use the <https://docs.github.com/en/free-pro-team@latest/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors|"Co-authored-by" feature> so that the original author (you) also gets credit for the final contribution in Github contribution stats. ---- 2020-10-26 17:42:58 UTC - Devin G. Bost: Yes, I'm totally fine with that. Thanks for thinking of including me in the stats as a contributor. +1 : Lari Hotari ---- 2020-10-27 05:09:22 UTC - Lari Hotari: > I’d recommend to pull the commonly failed tests in one of the github issues and break it up. @Sijie Guo Sounds like a plan. It looks like @eolivelli already created and fixed <https://github.com/apache/pulsar/issues/8374> , that was one of the common problems. I realized that it's possible to find the failed builds of your own PRs in <https://github.com/apache/pulsar/actions> by entering "is:failure actor:your_github_username" to the search. For example, my failed builds are <https://github.com/apache/pulsar/actions?query=is%3Afailure+actor%3Alhotari> . I'll be going through the failed builds in the upcoming days. I'd suggest that others do this too so that we could together get the CI flakiness under control asap. We can always check for the recently filed flaky test issues before creating new issues so that we don't create duplicates. /cc @Penghui Li ---- 2020-10-27 05:37:57 UTC - Lari Hotari: One of the common problems is the "Could not transfer artifact" error. `Could not transfer artifact org.objenesis:objenesis:jar:2.6 from/to central (<https://repo.maven.apache.org/maven2>): Transfer failed for <https://repo.maven.apache.org/maven2/org/objenesis/objenesis/2.6/objenesis-2.6.jar>: Connection reset` . Already reported by Devin as <https://github.com/apache/pulsar/issues/6231> . ---- 2020-10-27 05:57:00 UTC - Lari Hotari: PR to fix the maven download issue: <https://github.com/apache/pulsar/pull/8386> ----
