Re: [VOTE] (Take 3) Release Apache Cassandra 3.11.2

I ran the unit tests and they are green: https://circleci.com/gh/jasobrown/workflows/cassandra/tree/3.11.2-candidate-2 +1. Thanks, Michael. On Wed, Feb 14, 2018 at 1:34 PM, Nate McCall wrote: > +1 > > On Thu, Feb 15, 2018 at 10:09 AM, Michael Shuler

Re: [VOTE] (Take 3) Release Apache Cassandra 3.11.2

+1 On Thu, Feb 15, 2018 at 10:09 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.11.2. > > sha1: 1d506f9d09c880ff2b2693e3e27fa58c02ecf398 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.2-tentative

Re: [VOTE] (Take 2) Release Apache Cassandra 3.0.16

+1 On Thu, Feb 15, 2018 at 9:40 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.16. > > sha1: 890f319142ddd3cf2692ff45ff28e71001365e96 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.16-tentative

Re: [VOTE] (Take 3) Release Apache Cassandra 3.11.2

+1 On Wed, Feb 14, 2018 at 3:09 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.11.2. > > sha1: 1d506f9d09c880ff2b2693e3e27fa58c02ecf398 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= >

Re: [VOTE] (Take 2) Release Apache Cassandra 3.0.16

I ran the unit tests, and all are green: https://circleci.com/gh/jasobrown/workflows/cassandra/tree/3.0.16-candidate-2 +1. Thank you, Michael. On Wed, Feb 14, 2018 at 12:51 PM, Brandon Williams wrote: > +1 > > On Wed, Feb 14, 2018 at 2:40 PM, Michael Shuler

Re: [VOTE] (Take 2) Release Apache Cassandra 3.0.16

+1 On Wed, Feb 14, 2018 at 2:40 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.16. > > sha1: 890f319142ddd3cf2692ff45ff28e71001365e96 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= >

[VOTE] (Take 2) Release Apache Cassandra 3.0.16

I propose the following artifacts for release as 3.0.16. sha1: 890f319142ddd3cf2692ff45ff28e71001365e96 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.16-tentative Artifacts:

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

No worries.. it looks like we didn't update the circleci config in tree for the cassandra-3.0 and cassandra-3.11 branches. We should do that -- i'll take that as an action item on me... for now though you can grab the same one from trunk: CircleCI Configuration:

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

please use the latest circleci config that is in trunk. looking at the config you used in your run you’re using the old circleci 1.0 based config. > On Feb 14, 2018, at 10:16 AM, Michael Shuler wrote: > > So far, I have had very unpredictable test runs from CirceCI and

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

the tests are writing something to java.io.tmpdir which for whatever reason isn’t writable. the same exact tests work locally and in the cassandra-test docker image. given everyone can partake on circleci runs and asf jenkins i think we should send out those links and base the vote off those

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

This is an internal Jenkins instance that's not reachable on the internet. What's the permissions issue? The test runs on this internal instance are exactly the way cassci used to run - launch a scratch machine, check out, build, run tests. I'll see if I can repro locally. Michael On

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

On 02/14/2018 11:40 AM, Michael Shuler wrote: > Thanks for the feedback on 3.0.16 tentative release. > > Commit 890f319 (current cassandra-3.0 branch HEAD) fails only one test > (in both standard and -compression suites) in CI for me. This test has > failed 20 times in the last 20 runs. Test

Re: row tombstones as a separate sstable citizen

So is this at least a decent candidate for a feature request ticket? On Tue, Feb 13, 2018 at 8:09 PM, Carl Mueller wrote: > I'm particularly interested in getting the tombstones to "promote" up the > levels of LCS more quickly. Currently they get attached at the

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

i looked at this a few weeks back. this is asf jenkins right? if so, it’s a permissions issue on the build executors > On Feb 14, 2018, at 9:40 AM, Michael Shuler wrote: > > Thanks for the feedback on 3.0.16 tentative release. > > Commit 890f319 (current cassandra-3.0

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

Hi Michael, Which CI environment? iirc, I had several clean runs in circleci with the latest commits (will run again today). Thanks, -Jasoin On Wed, Feb 14, 2018 at 9:40 AM, Michael Shuler wrote: > Thanks for the feedback on 3.0.16 tentative release. > > Commit

[VOTE FAILED] Release Apache Cassandra 3.0.16

Thanks for the feedback on 3.0.16 tentative release. Commit 890f319 (current cassandra-3.0 branch HEAD) fails only one test (in both standard and -compression suites) in CI for me. This test has failed 20 times in the last 20 runs. Test output attached. Do we wish to fix this before the next

[VOTE FAILED] (Take 2) Release Apache Cassandra 3.11.2

Thanks for all the feedback on this tentative release commit. Commit 1d506f9 (current cassandra-3.11 branch HEAD) just passed testall 100% for me in CI, so I'll get a new artifact set up soon for Take 3. -- Warm regards, Mcihael On 02/14/2018 07:30 AM, Jason Brown wrote: > CASSANDRA-14234

Apache EU Roadshow CFP Closing Soon (23 February)

Hello Everyone This is an initial reminder to let you all know that we are holding an Apache EU Roadshow co-located with FOSS Backstage in Berlin on 13^th and 14^th June 2018. https://s.apache.org/tCHx The Call for Proposals (CFP) for the Apache EU Roadshow is currently open and will close

Re: [VOTE] Release Apache Cassandra 3.0.16

I think we can attempt another build and vote now. On Tue, Feb 13, 2018 at 3:44 PM, Jason Brown wrote: > CASSANDRA-14219 is committed and tests look clean (https://circleci.com/ > workflow-run/d0a2622a-e74f-4c46-b0ad-a84ca063736f). > > On Tue, Feb 13, 2018 at 1:47 PM,

Re: [VOTE] (Take 2) Release Apache Cassandra 3.11.2

CASSANDRA-14234 (which fixes ReadCommandTest) is now committed. I think we can attempt another build and vote. Thanks, -Jason On Tue, Feb 13, 2018 at 6:16 PM, Jason Brown wrote: > Thank you, Kurt. I'll get to it within the next 12-24 hours (kids' > homework time in the