Dear community,
I would like to propose the first test artifact of Apache Cassandra Sidecar.
The 0.1 release includes many features, and there are many upcoming
exciting features coming to the Sidecar. Summary of features can be
found in the NEWS file[2].
The test build of Cassandra Sidecar
The test build of Cassandra 5.0.3 is available.
sha1: b0226c8ea122c3e5ea8680efb0744d33924fd732
Git: https://github.com/apache/cassandra/tree/5.0.3-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1360/org/apache/cassandra/cassandra-all/5.0.3/
The
The test build of Cassandra 4.1.8 is available.
sha1: 044727aabafeab2f6fef74c52d349d55c8732ef5
Git: https://github.com/apache/cassandra/tree/4.1.8-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1359/org/apache/cassandra/cassandra-all/4.1.8/
The
The test build of Cassandra 4.0.16 is available.
sha1: c989c02be66411991c8536ca00ee6481f43e642e
Git: https://github.com/apache/cassandra/tree/4.0.16-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1358/org/apache/cassandra/cassandra-all/4.0.16
The test build of Cassandra 3.11.18 is available.
sha1: 429f3ad83e1c9eff5c288a7c8fb4781939d00090
Git: https://github.com/apache/cassandra/tree/3.11.18-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1357/org/apache/cassandra/cassandra-all/3.11.18
The test build of Cassandra 3.0.31 is available.
sha1: 09e7a4d6ae23b7ac5c9867235c9d900d0c99649a
Git: https://github.com/apache/cassandra/tree/3.0.31-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1356/org/apache/cassandra/cassandra-all/3.0.31
The test build of Cassandra 5.0.2 is available.
sha1: f278f6774fc76465c182041e081982105c3e7dbb
Git: https://github.com/apache/cassandra/tree/5.0.2-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1349/org/apache/cassandra/cassandra-all/5.0.2/
The
The test builds of Cassandra 4.0.14, 4.1.7 and 5.0.1, are available.
A vote of this test build will be initiated within the next couple of days.
== 4.0.14 ==
sha1: 7bf67349579411521bcdee4febd209cff63179a6
Git: https://github.com/apache/cassandra/tree/4.0.14-tentative
Maven Artifacts:
https
+1
> On 10 Sep 2024, at 15:34, Doug Rohrer wrote:
>
> Proposing the test build of in-jvm dtest API 0.0.17 for release
>
> Repository:
> https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git
>
> Candidate SHA:
> https://github.com/apache/cassan
+1 nb
> On Sep 10, 2024, at 7:34 AM, Doug Rohrer wrote:
>
> Proposing the test build of in-jvm dtest API 0.0.17 for release
>
> Repository:
> https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git
>
> Candidate SHA:
> https://github.com/apache/cassan
+1
On Tue, Sep 10, 2024, at 11:07 AM, Michael Shuler wrote:
> +1
>
> On 9/10/24 09:34, Doug Rohrer wrote:
> > Proposing the test build of in-jvm dtest API 0.0.17 for release
> >
> > Repository:
> > https://gitbox.apache.org/repos/asf?p=cassandra
+1
On 9/10/24 09:34, Doug Rohrer wrote:
Proposing the test build of in-jvm dtest API 0.0.17 for release
Repository:
https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git
<https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git>
Candidate SHA:
https://gith
+1
Kind Regards,
Brandon
On Tue, Sep 10, 2024 at 9:36 AM Doug Rohrer wrote:
>
> Proposing the test build of in-jvm dtest API 0.0.17 for release
>
> Repository:
> https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git
>
> Candidate SHA:
> https://github.com
>
> The vote will be open for 24 hours. Everyone who has tested the build
> is invited to vote. Votes by PMC members are considered binding. A
> vote passes if there are at least three binding +1s.
>
+1
The test build of Cassandra 5.0.0 GA is available.
sha1: 186272edca920c757b91bf95c2392bafa1a38d72
Git: https://github.com/apache/cassandra/tree/5.0.0-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1342/org/apache/cassandra/cassandra-all/5.0.0
The test build of Cassandra 5.0-rc2 is available.
sha1: 06691fce25a215361332aa1767e188bb6694687a
Git: https://github.com/apache/cassandra/tree/5.0-rc2-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1341/org/apache/cassandra/cassandra-all/5.0-rc2
The test build of Cassandra 5.0-rc1 is available.
sha1: b43f0b2e9f4cb5105764ef9cf4ece404a740539a
Git: https://github.com/apache/cassandra/tree/5.0-rc1-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1336/org/apache/cassandra/cassandra-all/5.0-rc1
Thanks for the links. Checked the latest ci-cassandra 4.1 runs [1][2][3]
and looks like the only consistently flaky across these runs is
MemtableSizeTest being tracked on CASSANDRA-17298 so I think we're good to
go.
[1] https://ci-cassandra.apache.org/job/Cassandra-4.1/461/
[2] https://ci-cassandr
> cassandra-4.1 branch in Jenkins is disabled so we can't have any builds
> from there for now.
>
Running: https://ci-cassandra.apache.org/job/Cassandra-4.1/461/
(without arm agents – we are waiting on them getting reconfigured)
disabled so we can't have any builds
from there for now.
I'll ask around for somebody to run the upgrades as well.
On Thu, Feb 1, 2024 at 4:26 AM Paulo Motta wrote:
> Is there a CI test run of this release candidate tag available ?
>
> Fwiw, docker image build (verify b
Is there a CI test run of this release candidate tag available ?
Fwiw, docker image build (verify binary gpg+sha512sum) + jre11 startup
looks good with:
CASSANDRA_VERSION=4.1.4;docker build -t
apache/cassandra-test:$CASSANDRA_VERSION --build-arg
CASSANDRA_VERSION=$CASSANDRA_VERSION --build-arg
@cassandra.apache.org
*Subject: *Re: [ANNOUNCE] Apache Cassandra 4.1.4 test artifact available
Silly question but there was just a 4.0.12 release, should users avoid
adopting that or is the concern more cantered around CI and testing?
Does a 4.0.13 need to be considered?
Regards,
**
*Jackson
@cassandra.apache.org
*Subject: *Re: [ANNOUNCE] Apache Cassandra 4.1.4 test artifact available
Silly question but there was just a 4.0.12 release, should users avoid
adopting that or is the concern more cantered around CI and testing?
Does a 4.0.13 need to be considered?
Regards,
**
*Jackson *
*From
Sorry centered not “cantered”
From: Fleming, Jackson
Date: Wednesday, 24 January 2024 at 6:29 pm
To: dev@cassandra.apache.org
Subject: Re: [ANNOUNCE] Apache Cassandra 4.1.4 test artifact available
Silly question but there was just a 4.0.12 release, should users avoid adopting
that or is the
Subject: Re: [ANNOUNCE] Apache Cassandra 4.1.4 test artifact available
EXTERNAL EMAIL - USE CAUTION when clicking links or attachments
-1
I just raised CASSANDRA-19097 (4.0->5.0) to critical. Basically we fail
to bootstrap correctly and even reading at ALL after bootstrapping fails
to get
the code
welcomed.
On 23/1/24 21:03, Štefan Miklošovič wrote:
The test build of Cassandra 4.1.4 is available.
sha1: 99d9faeef57c9cf5240d11eac9db5b283e45a4f9
Git: https://github.com/apache/cassandra/tree/4.1.4-tentative
Maven Artifacts:
https://repository.apache.org/content/repo
The test build of Cassandra 4.1.4 is available.
sha1: 99d9faeef57c9cf5240d11eac9db5b283e45a4f9
Git: https://github.com/apache/cassandra/tree/4.1.4-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1324/org/apache/cassandra/cassandra-all/4.1.4/
The
The test build of Cassandra 4.0.12 is available.
sha1: af752fcd535ccdac69b9fed88047b2dd7625801e
Git: https://github.com/apache/cassandra/tree/4.0.12-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1323/org/apache/cassandra/cassandra-all/4.0.12
+1
> On Dec 15, 2023, at 7:35 PM, Mick Semb Wever wrote:
>
>
>
>> I'd like to add Semver4j to the production dependencies. It is currently on
>> the test classpath. The library is pretty lightweight, licensed with MIT and
>> has no transitive dependenci
I'd like to add Semver4j to the production dependencies. It is currently on
> the test classpath. The library is pretty lightweight, licensed with MIT
> and has no transitive dependencies.
>
> We need to represent the kernel version somehow in CASSANDRA-19196 and
> Semver4j loo
e concern I guess.
>
> Cheers,
>
> Derek
>
> On Fri, Dec 15, 2023 at 2:56 AM Jacek Lewandowski
> wrote:
>> Hi,
>>
>> I'd like to add Semver4j to the production dependencies. It is currently on
>> the test classpath. The library is pretty light
lt;
lewandowski.ja...@gmail.com> wrote:
> Hi,
>
> I'd like to add Semver4j to the production dependencies. It is currently
> on the test classpath. The library is pretty lightweight, licensed with MIT
> and has no transitive dependencies.
>
> We need to represent th
Hi,
I'd like to add Semver4j to the production dependencies. It is currently on
the test classpath. The library is pretty lightweight, licensed with MIT
and has no transitive dependencies.
We need to represent the kernel version somehow in CASSANDRA-19196 and
Semver4j looks as the right too
The test build of Cassandra Java Driver 4.18.0 is available.
sha1: 105d378fce16804a8af4c26cf732340a0c63b3c9
Git: https://github.com/apache/cassandra-java-driver/tree/4.18.0
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1322
<https://repository.apache.
The test build of Cassandra 5.0-alpha2 is available.
DISCLAIMER, this alpha release does not contain the features:
Transactional Cluster Metadata
(CEP-21) and Accord Transactions (CEP-15). These features are under
discussion to be pushed to a 5.1-alpha1 release, with an eta still
this year
+1
From: David Capwell
Sent: Wednesday, September 13, 2023 3:44 PM
To: dev
Subject: [EXTERNAL] [DISCUSS] Add Jepsen's Elle as a test dependency for Accord
/ Paxos
For validation of Paxos and Accord 2 different consistency verifiers were
cr
We can't use open-nlp because it is JDK 17 only. I'll pull the smile-nlp
dependency and write something to do the same thing. Our usage was trivial.
On Thu, 14 Sept 2023 at 00:10, J. D. Jordan
wrote:
> Reading through smile license again, it is licensed pure GPL 3, not GPL
> with classpath excep
Reading through smile license again, it is licensed pure GPL 3, not GPL with classpath exception. So I think that kills all debate here.-1 on inclusion On Sep 13, 2023, at 2:30 PM, Jeremiah Jordan wrote:
I wonder if it can easily be replaced with Apache open-nlp? It also provides an implemen
For validation of Paxos and Accord 2 different consistency verifiers were
created: accord.verify.StrictSerializabilityVerifier (Accord), and
org.apache.cassandra.simulator.paxos.LinearizabilityValidator (Paxos). To
increase confidence in both protocols it would be good to use an external
consi
I wonder if it can easily be replaced with Apache open-nlp? It also
provides an implementation of GloVe.
https://opennlp.apache.org/docs/2.3.0/apidocs/opennlp-tools/opennlp/tools/util/wordvector/Glove.html
On Sep 13, 2023 at 1:17:46 PM, Benedict wrote:
> There’s a distinction for spotbugs an
There’s a distinction for spotbugs and other build related tools where they can be downloaded and used during the build so long as they’re not critical to the build process.They have to be downloaded dynamically in binary form I believe though, they cannot be included in the release.So it’s not rea
On Wed, Sep 13, 2023 at 11:37 AM Jeff Jirsa wrote:
> You can open a legal JIRA to confirm, but based on my understanding (and
> re-confirming reading
> https://www.apache.org/legal/resolved.html#category-a ):
>
>
We should probably get clarification here regardless, iirc this came up
when we were
since
the PROJECT ships SOURCE to build the product, if the SOURCE to build
requires the test, the test is clearly non-optional)
- GPL is cat X https://www.apache.org/legal/resolved.html#category-x
Cat X mixes "project" and "product" a few times, but again, the product is
still the
t; The reason for this library is that we found that using random vectors
>>> in testing produced very inconsistent results. Using the smile-nlp word2vec
>>> implementation with the glove.3k.50d library produces repeatable results.
>>>
>>> Does anyone have any obj
put into the HNSW graph index.
>>
>> The reason for this library is that we found that using random vectors in
>> testing produced very inconsistent results. Using the smile-nlp word2vec
>> implementation with the glove.3k.50d library produces repeatable results.
>>
>
d library produces repeatable results.
>
> Does anyone have any objections to the use of this library as a test only
> dependency?
> --
> [image: DataStax Logo Square] <https://www.datastax.com/> *Mike Adamson*
> Engineering
>
> +1 650 389 6000 <16503896000> | datast
that using random vectors in
testing produced very inconsistent results. Using the smile-nlp word2vec
implementation with the glove.3k.50d library produces repeatable results.
Does anyone have any objections to the use of this library as a test only
dependency?
--
[image: DataStax Logo Square] <ht
The test build of Cassandra 5.0-alpha1 is available.
DISCLAIMER this alpha release does not contain the expected 5.0
features: Vector Search (CEP-30), Transactional Cluster Metadata
(CEP-21) and Accord Transactions (CEP-15). These features will land
in a later alpha release.
sha1
The test build of Cassandra 3.11.16 is available.
sha1: f86929eae086aa108cf58ee0164c3d12a59ad4af
Git: https://github.com/apache/cassandra/tree/3.11.16-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1305/org/apache/cassandra/cassandra-all/3.11.16
rity.x509 package. You can still generate
> a Self-Signed certificate using BouncyCastle by adding it to the classpath,
> described
> in this issue <https://github.com/netty/netty/issues/10317> from the
> Netty community. We plan to add BountyCastle test dependency as part of
> C
ues/10317> from the Netty
community. We plan to add BountyCastle test dependency as part of
CASSANDRA-17992, which will fix SSLFactoryTest. Please let us know if you
have any questions or concerns.
Best regards,
Ekaterina
The test build of Cassandra 4.1.3 is available.
sha1: 2a4cd36475de3eb47207cd88d2d472b876c6816d
Git: https://github.com/apache/cassandra/tree/4.1.3-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1304/org/apache/cassandra/cassandra-all/4.1.3/
The
+1
Checked debian and boolean redhat installs
Kind Regards,
Brandon
On Wed, Jul 12, 2023 at 3:08 PM Miklosovic, Stefan
wrote:
>
> The test build of Cassandra 4.0.11 is available.
>
> sha1: f8584b943e7cd62ed4cb66ead2c9b4a8f1c7f8b5
> Git: https://github.com/apache/cassandra/tree/4
The test build of Cassandra 4.0.11 is available.
sha1: f8584b943e7cd62ed4cb66ead2c9b4a8f1c7f8b5
Git: https://github.com/apache/cassandra/tree/4.0.11-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1303/org/apache/cassandra/cassandra-all/4.0.11
ub.com/wiremock/wiremock/issues/1655
>
> Kind Regards,
> Brandon
>
> On Tue, Jun 20, 2023 at 6:35 AM Miklosovic, Stefan
> wrote:
> >
> > Hi,
> >
> > we want to introduce wiremock library (1) into the project as a test
> dependency to test CASSANDRA-16555.
t; > Hi,
> >
> > we want to introduce wiremock library (1) into the project as a test
> > dependency to test CASSANDRA-16555.
> >
> > In that patch, (wip here (2)), we want to test how would such snitch behave
> > based on what Amazon EC2 Identity Service of vers
at 6:35 AM Miklosovic, Stefan
wrote:
>
> Hi,
>
> we want to introduce wiremock library (1) into the project as a test
> dependency to test CASSANDRA-16555.
>
> In that patch, (wip here (2)), we want to test how would such snitch behave
> based on what Amazon EC2 Identity Ser
retty much imagine that
the testing efforts might be expanded to all other snitches as well.
From: Miklosovic, Stefan
Sent: Tuesday, June 20, 2023 13:35
To: dev@cassandra.apache.org
Subject: Adding wiremock to test dependencies
Hi,
we want to introduce wiremo
Hi,
we want to introduce wiremock library (1) into the project as a test dependency
to test CASSANDRA-16555.
In that patch, (wip here (2)), we want to test how would such snitch behave
based on what Amazon EC2 Identity Service of version 2 returned to that snitch.
AWS Identity service of
The test build of Cassandra 3.0.29 is available.
sha1: 087cffce636b63c12e328994d52bdf8f4ccc9750
Git: https://github.com/apache/cassandra/tree/3.0.29-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1288/org/apache/cassandra/cassandra-all/3.0.29
The test build of Cassandra 3.11.15 is available.
sha1: 6cdcf5e56a77cf40c251125d68856a614eccbc53
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.15-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1287/org
Based on this thread (1) I want to initiate the release process of 4.0.9.
The test build of Cassandra 4.0.9 is available.
sha1: 99f62b7338fc97a150e52e285f4eee3c636d6637
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.9-tentative
Maven Artifacts:
https
The test build of Cassandra 4.1.1 is available.
sha1: 8d91b469afd3fcafef7ef85c10c8acc11703ba2d
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.1.1-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1284/org/apache
AM, Derek Chen-Becker wrote:
>
> Do we have the hsqldb library just for a primitive oriented equivalent of
> Map? If this is test code only that seems like a pretty easy thing
> to replace and I would vote to implement that so we can fully drop the
> dependency.
>
> Cheers
Do we have the hsqldb library just for a primitive oriented equivalent of
Map? If this is test code only that seems like a pretty easy
thing to replace and I would vote to implement that so we can fully drop
the dependency.
Cheers,
Derek
On Tue, Mar 14, 2023 at 5:49 AM Miklosovic, Stefan
o spend time on rewriting this and then we remove Hadoop
> libraries or I just add this library among the test ones?
>
> Thanks
>
> (1) https://github.com/apache/cassandra/pull/2212/files#r1133841928
are depending
on hsqldb in simulator package. Can not we rewrite that so we can drop this
dependency entirely?
Do we want to spend time on rewriting this and then we remove Hadoop libraries
or I just add this library among the test ones?
Thanks
(1) https://github.com/apache/cassandra/pull/2212
Hi guys,
This is my first time doing this, I am driving the release of 4.0.8 to learn
the process etc.
The test build of Cassandra 4.0.8 is available.
sha1:
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.8-tentative
Maven Artifacts:
https
: Thursday, January 12, 2023 14:59
To: dev@cassandra.apache.org
Subject: Re: Introducing mockito-inline library among test dependencies
NetApp Security WARNING: This is an external email. Do not click links or open
attachments unless you recognize the sender and know the content is safe.
Hi Jacek
that I wanted to mock static methods like two years ago and I hit
the very same issue back then as I do now (1).
Please keep in mind that the error is not related to what I wanted to test for
CASSANDRA-14361, it is rather the consequence of us including mockito-inline to
mock static methods and
Will it work with Java17?
czw., 12 sty 2023, 12:56 użytkownik Brandon Williams
napisał:
> +1
>
> Kind Regards,
> Brandon
>
> On Wed, Jan 11, 2023 at 2:02 PM Miklosovic, Stefan
> wrote:
> >
> > Hi list,
> >
> > the test for (1) is using mockito-inli
+1
Kind Regards,
Brandon
On Wed, Jan 11, 2023 at 2:02 PM Miklosovic, Stefan
wrote:
>
> Hi list,
>
> the test for (1) is using mockito-inline dependency for mocking static
> methods as mockito-core is not able to do that on its own. mockito-inline was
> not part of our test
s/mockito-extensions
> )
>
> On Jan 11, 2023, at 12:02 PM, Miklosovic, Stefan <
> stefan.mikloso...@netapp.com> wrote:
>
> Hi list,
>
> the test for (1) is using mockito-inline dependency for mocking static
> methods as mockito-core is not able to do that on its own.
ain/resources/mockito-extensions>)
> On Jan 11, 2023, at 12:02 PM, Miklosovic, Stefan
> wrote:
>
> Hi list,
>
> the test for (1) is using mockito-inline dependency for mocking static
> methods as mockito-core is not able to do that on its own. mockito-inline was
> not
Hi list,
the test for (1) is using mockito-inline dependency for mocking static methods
as mockito-core is not able to do that on its own. mockito-inline was not part
of our test dependencies prior this work. I want to ask if we are all OK with
being able to mock static methods from now on
> The test build of Cassandra 4.1.0 is available.
Our requirements for 4.1-rc were one green CI run. And no regression
flakies (except the two we have waivers for).
Three consecutive jdk8 and jdk11 circleci runs can be found in these lists:
jdk8
https://app.circleci.com/pipelines/git
The test build of Cassandra 4.1.0 is available. This is an early staging
announcement.
sha1: b807f97b37933fac251020dbd949ee8ef245b158
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.1.0-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories
>
> The test build of Cassandra 4.1-rc1 is available.
>
Our requirements for 4.1-rc were one green CI run. And no regression
flakies (except the two we have waivers for).
The green circleci runs are here:
-
https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/40/
The test build of Cassandra 4.1-rc1 is available.
sha1: d6822c45ae3d476bc2ff674cedf7d4107b8ca2d0
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.1-rc1-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1280/org/apache
the resources(compared to max out) for some suites we get similar
> and reasonable time to run for those test suites.
> One confusion I want to clear here - MIDRES doesn’t mean we will use
> medium containers but mid/less than the HIGHRES resources. Some Python
> tests cannot be run
hich proved that with half the
> resources(compared to max out) for some suites we get similar and reasonable
> time to run for those test suites.
> One confusion I want to clear here - MIDRES doesn’t mean we will use medium
> containers but mid/less than the HIGHRES resources. Some Python tes
(compared to max out) for some suites we get similar
and reasonable time to run for those test suites.
One confusion I want to clear here - MIDRES doesn’t mean we will use
medium containers but mid/less than the HIGHRES resources. Some Python
tests cannot be run with medium containers, for example
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 alter
> * 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 pushe
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
The test build of Cassandra 4.1-beta1 is available.
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-1276/org
The test build of Cassandra 4.0.6 is available.
>
> sha1:
>
The sha is eb2375718483f4c360810127ae457f2a26ccce67
The test build of Cassandra 4.0.6 is available.
sha1:
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.6-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1275/org/apache/cassandra/cassandra-all/4.0.6/
The Source
The test build of Cassandra 4.0.5 is available.
sha1: ec476e0e259efb62ee19804c3ff46dbbe4d1ded7
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.5-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1274/org/apache
Hi All,
if I am parsing this thread correctly it seems we have a number of
options to attack and some are already progressing: tmp misconfig,
docker misconfig, unmatched resources in different CI envs, no
definition of minimal HW requiremenets, etc.
But so far nothing against merging CASSAND
However, the docker space
> issue needs to be resolved first since we don't have the capacity to
> experiment with those nodes out of commission.
>
ETA on fixing the docker space issues is this/next week. Once that lands we
can take a look at the abnormal CPU usage on some nodes.
time* - is that a bug?
>
>
> I'd say it is a bug in the test if we can't distinguish between the test
> failing and the test not completing/crashing. How much time folk want to
> spend on the different test frameworks we have to improve such things (on a
> distribut
ons in expected time,
> completely time out, fall over, or otherwise *preserve correctness but
> die or don't complete operations in time* - is that a bug?
>
I'd say it is a bug in the test if we can't distinguish between the test
failing and the test not completing/crash
me out, fall over, or otherwise *preserve correctness but
> die or don't complete operations in time* - is that a bug?
>
> And if the angle is more "the test isn't deterministic and fails on
> under-provisioned hosts; there's a bug *in the test*", well, that'
rs, and the
nodes take so long with GC pauses, compaction, streaming, etc that they don't
correctly complete certain operations in expected time, completely time out,
fall over, or otherwise *preserve correctness but die or don't complete
operations in time* - is that a bug?
And if th
I suspect there's another problem with some of the Jenkins nodes where
the system CPU usage is high and drives the load much higher than
other nodes, possibly causing timeouts. However, the docker space
issue needs to be resolved first since we don't have the capacity to
experiment with those nodes
Another option would be to increase the resources dedicated to each agent
container and run less in parallel. Or, best yet, do both (up timeouts and
lower parallelization / up resources).
As far as I can tell the failures on Jenkins aren't value-add compared to what
we're seeing on circleci and
Hi All,
bringing https://issues.apache.org/jira/browse/CASSANDRA-17729 to the ML
for visibility as this has been a discussion point with some of you.
I noticed tests timeout much more on jenkins that circle. I was
wondering if legit bugs were hiding behind those timeouts and it might
be the
The test build of Cassandra 4.1-alpha1 is available.
sha1: 6f05be447073925a7f3620ddbbd572aa9fcd10ed
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.1-alpha1-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1273/org
The test build of Cassandra 4.0.4 is available.
sha1: 052125f2c6ed308f1473355dfe43470f0da44364
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.4-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1270/org/apache
1 - 100 of 296 matches
Mail list logo
