Happy to help! Certainly getting Circle CI and ASF CI at parity seems like a good goal. I'm going to probably have some extra cycles next week while I'm at ApacheCon, so I'm hoping to make some meaningful progress :)
Cheers, Derek On Mon, Sep 26, 2022 at 12:44 PM Ekaterina Dimitrova <e.dimitr...@gmail.com> wrote: > Thanks Josh for bringing this up. > I agree with Brandon on both points he made. > I have also other examples of testing some things only in Jenkins or only > in CircleCI. If people are fine with that, I can open a ticket and I just > talked n Slack to Derek who expressed interest to help with that activity. > Thanks in advance Derek, this will be great support for the project. > > On Mon, 26 Sep 2022 at 14:15, Brandon Williams <dri...@gmail.com> wrote: > >> On Mon, Sep 26, 2022 at 12:20 PM Josh McKenzie <jmcken...@apache.org> >> wrote: >> > For CI on a patch, run the pre-commit suite and also run multiplexer >> with 250 runs on new, changed, or related tests to ensure not flaky >> >> 250 iterations isn't enough; I use 500 as a low water mark. >> >> > I think it's worth calling out: relying on circleci test runs along >> with ASF CI as an option implies we have the same confidence in a green >> circleci run as we have in a green ASF CI run. >> >> This is also assuming that circle and ASF CI run the same tests, which >> is not entirely true. We know that circle isn't running some upgrade >> tests from https://issues.apache.org/jira/browse/CASSANDRA-17912 but I >> think we need to specifically investigate parity between the two >> systems for further discrepancies before we can begin to compare >> confidence in runs between them. >> > -- +---------------------------------------------------------------+ | Derek Chen-Becker | | GPG Key available at https://keybase.io/dchenbecker and | | https://pgp.mit.edu/pks/lookup?search=derek%40chen-becker.org | | Fngrprnt: EB8A 6480 F0A3 C8EB C1E7 7F42 AFC5 AFEE 96E4 6ACC | +---------------------------------------------------------------+
