Re: reroll the builds?

If that's the case, I'm +1 on rerolling the builds. Dinesh On Tuesday, July 24, 2018, 9:18:14 AM PDT, Jason Brown wrote: I did run the dtests against the last release shas (3.0.16 and 3.11.2). Notes are all the way at the bottom of the gist about those runs. Circleci URLs:

Re: reroll the builds?

I did run the dtests against the last release shas (3.0.16 and 3.11.2). Notes are all the way at the bottom of the gist about those runs. Circleci URLs: https://circleci.com/workflow-run/5a1df5a1-f0c1-4ab4-a7db-e5551e7a5d38 / https://circleci.com/workflow-run/a4369ab0-ae11-497a-8e10-de3995d10f25.

Re: reroll the builds?

Hi Jason, I agree - we should release with the dataloss bug fix. I went over the gist - apart from the Python errors and test teardown failures, there seem to be a few failures that look legitimate. Any chance you can run the dtests on the previous release SHAs and compare the dtest failures?

Re: reroll the builds?

TL;DR We are in a better place than we were for the 3.0.16 and 3.11.2 releases. The current fails are not fatal, although they warrant investigation. My opinion is that due the critical data loss bugs that are fixed by CASSANDRA-14513 and CASSANDRA-14515, we should cut the builds now. I've run

Re: reroll the builds?

I can help out with the triage / rerunning dtests if needed. Dinesh On Monday, July 23, 2018, 10:22:18 AM PDT, Jason Brown wrote: I spoke with some people over here, and I'm going to spend a day doing a quick triage of the failing dtests. There are some fixes for data loss bugs that

Re: reroll the builds?

I spoke with some people over here, and I'm going to spend a day doing a quick triage of the failing dtests. There are some fixes for data loss bugs that are critical to get out in these builds, so I'll ensure the current failures are within an acceptable level of flakey-ness in order to unblock

Re: reroll the builds?

Hi all, First, thanks Joey for running the tests. Your pass/fail counts are basically what in line with what I've seen for the last several months. (I don't have an aggregated list anywhere, just observations from recent runs). Second, it's beyond me why there's such inertia to actually cutting

Re: reroll the builds?

We ran the tests against 3.0, 2.2 and 3.11 using circleci and there are various failing dtests but all three have green unit tests. 3.11.3 tentative (31d5d87, test branch , unit tests

Re: reroll the builds?

On 07/16/2018 11:27 PM, Jason Brown wrote: > Hey all, > > The recent builds were -1'd, but it appears the issues have been resolved > (2.2.13 with CASSANDRA-14423, and 3.0.17 / 3.11.3 reverting > CASSANDRA-14252). Can we go ahead and reroll now? Could someone run through the tests on 2.2, 3.0,