Re: [VOTE] Release Apache Cassandra 3.0.21
+1 On Tue, Jul 14, 2020, 5:50 PM Mick Semb Wever wrote: > Proposing the test build of Cassandra 3.0.21 for release. > > sha1: e39d1da325f5853ab3a64d92ecf52f8271239b9e > Git: > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.21-tentative > Maven Artifacts: > > https://repository.apache.org/content/repositories/orgapachecassandra-1208/org/apache/cassandra/cassandra-all/3.0.21/ > > The Source and Build Artifacts, and the Debian and RPM packages and > repositories, are available here: > https://dist.apache.org/repos/dist/dev/cassandra/3.0.21/ > > The vote will be open for 72 hours (longer if needed). 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]: CHANGES.txt: > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.0.21-tentative > [2]: NEWS.txt: > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/3.0.21-tentative >
Re: [VOTE] Release Apache Cassandra 3.11.7
Ran following circleCI tests j8_unit_tests (1 failing) - testIndexMemtableSwitching - org.apache.cassandra.index.sasi.SASIIndexTest with exception junit.framework.AssertionFailedError: expected:<0> but was:<1>, at org.apache.cassandra.index.sasi.SASIIndexTest.testIndexMemtableSwitching(SASIIndexTest.java:2379) j8_jvm_dtests (PASS) j8_dtests (3 failing, each in with vnodes and no-vnodes) On Wed, Jul 15, 2020 at 12:23 PM Eric Evans wrote: > +1 > > On Tue, Jul 14, 2020 at 5:47 PM Mick Semb Wever wrote: > > > > Proposing the test build of Cassandra 3.11.7 for release. > > > > sha1: 9fe62b3e40147fda2cc081744bd375b04574aef7 > > Git: > > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.7-tentative > > Maven Artifacts: > > > https://repository.apache.org/content/repositories/orgapachecassandra-1209/org/apache/cassandra/cassandra-all/3.11.7/ > > > > The Source and Build Artifacts, and the Debian and RPM packages and > > repositories, are available here: > > https://dist.apache.org/repos/dist/dev/cassandra/3.11.7/ > > > > The vote will be open for 72 hours (longer if needed). 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]: CHANGES.txt: > > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.11.7-tentative > > [2]: NEWS.txt: > > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/3.11.7-tentative > > > > -- > Eric Evans > eev...@apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
Re: [VOTE] Release Apache Cassandra 3.0.21
Ran following circleCI tests j8_unit_tests (PASS) j8_jvm_dtests (PASS) j8_dtests (5 failures, in each of with vnodes, and no-vnodes) On Tue, Jul 14, 2020 at 3:50 PM Mick Semb Wever wrote: > Proposing the test build of Cassandra 3.0.21 for release. > > sha1: e39d1da325f5853ab3a64d92ecf52f8271239b9e > Git: > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.21-tentative > Maven Artifacts: > > https://repository.apache.org/content/repositories/orgapachecassandra-1208/org/apache/cassandra/cassandra-all/3.0.21/ > > The Source and Build Artifacts, and the Debian and RPM packages and > repositories, are available here: > https://dist.apache.org/repos/dist/dev/cassandra/3.0.21/ > > The vote will be open for 72 hours (longer if needed). 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]: CHANGES.txt: > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.0.21-tentative > [2]: NEWS.txt: > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/3.0.21-tentative >
Re: [VOTE] Release Apache Cassandra 2.2.17
Ran following CircleCI tests j8_unit_tests (PASS) j8_jvm_dtests (1 failure "namedDcTest - org.apache.cassandra.distributed.test.NetworkTopologyTest" with "java.util.concurrent.TimeoutException") j8_dtests (60 failures in no-vnodes (all of them are from cqlsh_tests/test_cqlsh.py), 62 failures in vnodes (cqlsh_tests/test_cqlsh.py, bootstrap_test.py, rebuild_test.py) On Thu, Jul 16, 2020 at 9:41 AM Brandon Williams wrote: > +1 > > On Tue, Jul 14, 2020 at 5:53 PM Mick Semb Wever wrote: > > > > Proposing the test build of Cassandra 2.2.17 for release. > > > > sha1: cd006d275aa9b6e937c6ebd036d4d27c4ed18dbe > > Git: > > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.17-tentative > > Maven Artifacts: > > > https://repository.apache.org/content/repositories/orgapachecassandra-1207/org/apache/cassandra/cassandra-all/2.2.17/ > > > > The Source and Build Artifacts, and the Debian and RPM packages and > > repositories, are available here: > > https://dist.apache.org/repos/dist/dev/cassandra/2.2.17/ > > > > The vote will be open for 72 hours (longer if needed). 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]: CHANGES.txt: > > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/2.2.17-tentative > > [2]: NEWS.txt: > > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/2.2.17-tentative > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
Re: [VOTE] Release Apache Cassandra 4.0-beta1
+1 nb Ran following CircleCI tests j8_unit_tests (PASS) j8_jvm_dtests (PASS) j8_dtests (PASS) On Thu, Jul 16, 2020 at 10:18 AM Jordan West wrote: > +1 nb > > On Thu, Jul 16, 2020 at 9:38 AM Yifan Cai wrote: > > > +1 nb > > > > > > From: Robert Stupp > > Sent: Thursday, July 16, 2020 2:59:34 AM > > To: dev@cassandra.apache.org > > Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta1 > > > > +1 (nb) > > > > — > > Robert Stupp > > @snazy > > > > > On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang < > > zhaoyangsingap...@gmail.com> wrote: > > > > > > +1 (nb) > > > > > > On Thu, 16 Jul 2020 at 01:28, Brandon Williams > wrote: > > > > > >> +1 (binding) > > >> > > >> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever wrote: > > >> > > >>> Proposing the test build of Cassandra 4.0-beta1 for release. > > >>> > > >>> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004 > > >>> Git: > > >>> > > >>> > > >> > > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative > > >>> Maven Artifacts: > > >>> > > >>> > > >> > > > https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/ > > >>> > > >>> The Source and Build Artifacts, and the Debian and RPM packages and > > >>> repositories, are available here: > > >>> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/ > > >>> > > >>> The vote will be open for 72 hours (longer if needed). 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 and no > > >> -1s. > > >>> > > >>> Eventual publishing and announcement of the 4.0-beta1 release will be > > >>> coordinated, as described in > > >>> > > >>> > > >> > > > https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E > > >>> > > >>> [1]: CHANGES.txt: > > >>> > > >>> > > >> > > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative > > >>> [2]: NEWS.txt: > > >>> > > >>> > > >> > > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative > > >>> > > >> > > > > >
Re: [VOTE] Release Apache Cassandra 4.0-beta1
+1 nb On Thu, Jul 16, 2020 at 9:38 AM Yifan Cai wrote: > +1 nb > > > From: Robert Stupp > Sent: Thursday, July 16, 2020 2:59:34 AM > To: dev@cassandra.apache.org > Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta1 > > +1 (nb) > > — > Robert Stupp > @snazy > > > On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang < > zhaoyangsingap...@gmail.com> wrote: > > > > +1 (nb) > > > > On Thu, 16 Jul 2020 at 01:28, Brandon Williams wrote: > > > >> +1 (binding) > >> > >> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever wrote: > >> > >>> Proposing the test build of Cassandra 4.0-beta1 for release. > >>> > >>> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004 > >>> Git: > >>> > >>> > >> > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative > >>> Maven Artifacts: > >>> > >>> > >> > https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/ > >>> > >>> The Source and Build Artifacts, and the Debian and RPM packages and > >>> repositories, are available here: > >>> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/ > >>> > >>> The vote will be open for 72 hours (longer if needed). 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 and no > >> -1s. > >>> > >>> Eventual publishing and announcement of the 4.0-beta1 release will be > >>> coordinated, as described in > >>> > >>> > >> > https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E > >>> > >>> [1]: CHANGES.txt: > >>> > >>> > >> > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative > >>> [2]: NEWS.txt: > >>> > >>> > >> > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative > >>> > >> > >
Re: [VOTE] Release Apache Cassandra 2.2.17
+1 On Tue, Jul 14, 2020 at 5:53 PM Mick Semb Wever wrote: > > Proposing the test build of Cassandra 2.2.17 for release. > > sha1: cd006d275aa9b6e937c6ebd036d4d27c4ed18dbe > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.17-tentative > Maven Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1207/org/apache/cassandra/cassandra-all/2.2.17/ > > The Source and Build Artifacts, and the Debian and RPM packages and > repositories, are available here: > https://dist.apache.org/repos/dist/dev/cassandra/2.2.17/ > > The vote will be open for 72 hours (longer if needed). 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]: CHANGES.txt: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/2.2.17-tentative > [2]: NEWS.txt: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/2.2.17-tentative - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 4.0-beta1
+1 nb From: Robert Stupp Sent: Thursday, July 16, 2020 2:59:34 AM To: dev@cassandra.apache.org Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta1 +1 (nb) — Robert Stupp @snazy > On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang > wrote: > > +1 (nb) > > On Thu, 16 Jul 2020 at 01:28, Brandon Williams wrote: > >> +1 (binding) >> >> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever wrote: >> >>> Proposing the test build of Cassandra 4.0-beta1 for release. >>> >>> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004 >>> Git: >>> >>> >> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative >>> Maven Artifacts: >>> >>> >> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/ >>> >>> The Source and Build Artifacts, and the Debian and RPM packages and >>> repositories, are available here: >>> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/ >>> >>> The vote will be open for 72 hours (longer if needed). 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 and no >> -1s. >>> >>> Eventual publishing and announcement of the 4.0-beta1 release will be >>> coordinated, as described in >>> >>> >> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E >>> >>> [1]: CHANGES.txt: >>> >>> >> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative >>> [2]: NEWS.txt: >>> >>> >> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative >>> >>
Re: [VOTE] Release Apache Cassandra 4.0-beta1
+1 (nb) — Robert Stupp @snazy > On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang > wrote: > > +1 (nb) > > On Thu, 16 Jul 2020 at 01:28, Brandon Williams wrote: > >> +1 (binding) >> >> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever wrote: >> >>> Proposing the test build of Cassandra 4.0-beta1 for release. >>> >>> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004 >>> Git: >>> >>> >> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative >>> Maven Artifacts: >>> >>> >> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/ >>> >>> The Source and Build Artifacts, and the Debian and RPM packages and >>> repositories, are available here: >>> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/ >>> >>> The vote will be open for 72 hours (longer if needed). 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 and no >> -1s. >>> >>> Eventual publishing and announcement of the 4.0-beta1 release will be >>> coordinated, as described in >>> >>> >> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E >>> >>> [1]: CHANGES.txt: >>> >>> >> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative >>> [2]: NEWS.txt: >>> >>> >> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative >>> >>
Re: [DISCUSS] A point of view on Testing Cassandra
Thanks for getting the ball rolling. I think we need to be a lot more specific, though, and it may take some time to hash it all out. For starters we need to distinguish between types of "done" - are we discussing: - Release - New Feature - New Functionality (for an existing feature) - Performance Improvement - Minor refactor - Bug fix ? All of these (perhaps more) require unique criteria in my opinion. For example: - New features should be required to include randomised integration tests that exercise all of the functions of the feature in random combinations and verifies that the behaviour is consistent with expectation. New functionality for an existing feature should augment any existing such tests to include the new functionality in its random exploration of behaviour. - Releases are more suitable for many of your cluster-level tests, IMO, particularly if we get regular performance regression tests running against trunk (something for a shared roadmap) Then, there are various things that need specifying more clearly, e.g.: > Minimum 75% code coverage on non-boilerplate code Coverage by what? In my model, randomised integration tests of the relevant feature, but we need to agree specifically. Some thoughts: - Not clear the value of code coverage measures, but 75% perhaps an acceptable arbitrary number if we want a lower bound - More pertinent measure is options and behaviours - For a given system/feature/function, we should run with _every_ user option and every feature behaviour at least once; - Where tractable, exhaustive coverage (every combination of option, with every logical behaviour); - Where not possible, random combinations of options and behaviours. > - Some form of the above in mixed-version clusters I think we need to include mixed-schema, and modified-schema clusters as well, as this is a significant source of bugs > aggressively adversarial scenarios As far as chaos is concerned, I hope to bring an addition to in-jvm dtests soon, that should facilitate this for more targeted correctness tests - so problems can be surfaced more rapidly and repeatably. Also with much less hardware :) On 15/07/2020, 22:35, "Joshua McKenzie" wrote: I like that the "we need a Definition of Done" seems to be surfacing. No directed intent from opening this thread but it seems a serendipitous outcome. And to reiterate - I didn't open this thread with the hope or intent of getting all of us to agree on anything or explore what we should or shouldn't agree on. That's not my place nor is it historically how we seem to operate. :) Just looking to share a PoV so other project participants know about some work coming down the pipe and can engage if they're interested. Brainstorming here to get discussion started, which we could drop in a doc and riff on or high bandwidth w/collaborators interested in the topic: - Tested on clusters with N nodes (10? 50? 3?) <- I'd start at proposing min maybe 25 - Tested on data set sizes >= TB (Maybe 30 given the 25 node count w/current density) - Soak tested in aggressively adversarial scenarios w/proven correctness for 72 hours (fallout w/nodes down, up, bounce, GC pausing, major compaction, major repair, packet loss, bootstrapping, etc. We could come up with a list) - Some form of the above in mixed-version clusters - Minimum 75% code coverage on non-boilerplate code - Where possible (i.e. not a brand new semantic / feature), diff-tested against existing schemas making use of APIs in mixed version clusters as well as on new-version only clusters (in case of refactor / internal black box rewrite) Some discrete bars like the above for a definition of done may make sense. Any other ideas to add or differing points of view on what the #'s above should be? Or disagreement on the items in the list above? I hold all the above loosely, so don't hesitate to respond, disagree, or totally shoot down. Or propose an entirely different approach to determining a Definition of Done we could engage with. Last but not least, we'd have to make infrastructure like this available to the project at large for usage and validation on testing features or this exercise will simply serve to deter engagement with the project outside a small subset of the population with resources to dedicate to this type of testing which I think we don't want. On Wed, Jul 15, 2020 at 11:53 AM Benedict Elliott Smith wrote: > Perhaps you could clarify what you personally hope we _should_ agree as a > project, and what you want us to _not_ agree (blossom in infinite variety)? > > My view: We need to agree a shared framework for quality going forwards. > This will raise the bar to contributions, including above many that already > exist. So, we then
