I would add an option for generate.sh to detect all changed *Test.java
files, that would be handy imo.
On 28/9/22 4:29, Josh McKenzie wrote:
So:
1. 500 iterations on multiplexer
2. Augmenting generate.sh to allow providing multiple class names and
generating a single config that'll multi
So:
1. 500 iterations on multiplexer
2. Augmenting generate.sh to allow providing multiple class names and
generating a single config that'll multiplex all the tests provided
3. Test parity / pre-release config added on circleci (see
https://issues.apache.org/jira/browse/CASSANDRA-17930), spec
Could you please reply to me directly (off-list) if you will be in New
Orleans next week.
While we already have a list of the speakers, we would love to know in
advance who else in our dev community will be attending. (If you're reading
this you're in our dev community.)
regards,
Mick
We have a couple new test failures that came up as regressions recently:
https://issues.apache.org/jira/browse/CASSANDRA-17928
https://issues.apache.org/jira/browse/CASSANDRA-17927
Along with that, I'm not sure we're in a good spot from a "no flaky test"
perspective as per butler:
https://butler
“I have plans on modifying the multiplexer to allow specifying a list of
classes per test target, so we don't have to needlessly suffer with this”
That would be great, I was thinking of that the other day too. With that
said I’ll be happy to support you in that effort too :-)
On Tue, 27 Sep 202
> I have plans on modifying the multiplexer to allow specifying a list of
> classes per test target, so we don't have to needlessly suffer with this
This sounds integral to us multiplexing tests on large diffs whether we go with
circle for releases or not and would be a great addition!
On Tue, S
Proposing the test build of Cassandra 4.1-beta1 for release.
sha1: 5d9d93ea08d9c76402aa1d14bad54bf9ec875686
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.1-beta1-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-127
>
> 250 iterations isn't enough; I use 500 as a low water mark.
I agree that 500 iterations would be a reasonable minimum. We have seen
flaky unit tests requiring far more iterations, but that's not very common.
We could use to 500 iterations as default, and discretionary use a higher
limit in te
