The -h profile works but it spends a lot of resources for slightly faster results. The -m profile is better value in terms of speed per resources. I guess -h can be used if one wants to get results as soon as possible, no matter the cost. Ekaterina might be better informed than me, given her work on CASSANDRA-15712.
In any case, the new multiplexer doesn't change the resources configuration at all. We might want to reevaluate that config in the future, and probably follow David's suggestion of deciding parallelism as a function of the number of tests to be run. On Tue, 18 Oct 2022 at 18:13, Josh McKenzie <jmcken...@apache.org> wrote: > * Running the .circleci/generate.sh script with -l/-m/-h flags will use > git diff to automatically detect the new or modified tests and will add > them to the lists of tests to be repeated. The pre-commit workflow will > automatically start repeated runs for these tests. The only exception to > this are Python dtests, that should be specified manually. > > Of note: the -h profile should not be used (correct me if I'm wrong here > Andres). Use -l for the free tier on circle or -m for paid. > > Will have some follow up tickets regarding job naming, default config > type, and updating documentation shortly. > > On Tue, Oct 18, 2022, at 12:33 PM, Andrés de la Peña wrote: > > Just to let you know that CASSANDRA-17939 has just been committed. > > It changes the way the CircleCI multiplexer works, in line with the recent > changes in our release criteria: > > * The default number of repeated tests iterations is 500, except for long > and upgrade tests. > * It is possible to specify multiple test classes and methods to be > repeated into the same config push. So patches altering dozens of tests > won't require dozens of config pushes anymore. > * Running the .circleci/generate.sh script with -l/-m/-h flags will use > git diff to automatically detect the new or modified tests and will add > them to the lists of tests to be repeated. The pre-commit workflow will > automatically start repeated runs for these tests. The only exception to > this are Python dtests, that should be specified manually. > * The CircleCI jobs are rearranged so for every regular job there is a > companion job to run the repeated tests associated to that job. Those > companion jobs will only be visible if there are repeated tests to run. > Here > <https://app.circleci.com/pipelines/github/adelapena/cassandra/2278/workflows/e339f5d4-0e16-4d4a-bde8-f0d9b9f3912d> > is an example run with repeated tests for all the test suites, and here > <https://app.circleci.com/pipelines/github/adelapena/cassandra/2269/workflows/d8907cbc-dbca-4d21-bdb9-1a4c58e1a412> > is the same workflow without any repeated tests. > > Some documentation on how to use it can be found here: > https://github.com/apache/cassandra/blob/trunk/.circleci/readme.md#running-tests-in-a-loop > > >
