Hi all
We just wanted to give a heads up that we merged CEP-21, Transactional Cluster
Metadata to trunk[1] today.
There are about 15-20 flaky or failing tests in total, spread over several test
jobs[2] (i.e. single digit failures in a few of these). We have filed JIRAs for
the failures and ar
Hi everyone,
With TCM landed, there will be way more Harry tests in-tree: we are using it
for many coordination tests, and there's now a simulator test that uses Harry.
During development, Harry has allowed us to uncover and resolve numerous
elusive edge cases.
I had conversations with several
> I had conversations with several folks, and wanted to propose to move
> harry-core to Cassandra test tree. This will substantially
> simplify/streamline co-development of Cassandra and Harry. With a new
> HistoryBuilder API that has helped to find and trigger [1] [2] and [3], it
> will also be mu
> Yes. Any reason to have releases for users outside of Cassandra ? And is
> there any cross-branch/version interaction, like there is with the
> jvm-dtest-api ?
As of today, Harry tries not to rely on branch versions. Harry-core is
completely free of Cassandra dependency (for which I had to
I'm excited for Harry to come in-tree to improve the project stability and
quality. I know you're doing a talk at the Cassandra Summit about Harry to go
over it. If there's anything that can be done as part of this process to
improve onboarding for Harry too, that would be great. I'm just thi
Unfortunately my Harry talk got declined. Of course I’ll be happy to talk about
Harry and how it can be useful for contributors and about people’s
expectations. My talk is going to be about TCM again this time.
I will make sure examples are in place and are expressive by the summit.
On Fri, Nov
