Hi,
When we say all tests passing it does seem like we are including the
upgrade tests, but there are some failures that don't seem to have
tickets blocking the release. It seems like we are also excluding any
tests decorated as resource intensive? There is also large_dtest,
novnode_dtest, and off
Thanks! I think I was looking at a wrong JIRA, sorry 'bout that.
--
Michael
On 01/04/2017 12:31 PM, Oleksandr Petrov wrote:
> #13025 was updated yesterday. It just needs some feedback, but we know what
> the problem is there.
>
> On Wed, Jan 4, 2017 at 5:32 PM Michael Shuler
> wrote:
>
>> On
#13025 was updated yesterday. It just needs some feedback, but we know what
the problem is there.
On Wed, Jan 4, 2017 at 5:32 PM Michael Shuler
wrote:
> On 12/20/2016 03:48 PM, Michael Shuler wrote:
> > Current release blockers in JIRA on the cassandra-3.11 branch are:
> >
> > https://issues.apa
On 12/20/2016 03:48 PM, Michael Shuler wrote:
> Current release blockers in JIRA on the cassandra-3.11 branch are:
>
> https://issues.apache.org/jira/browse/CASSANDRA-12617
> https://issues.apache.org/jira/browse/CASSANDRA-13058
and https://issues.apache.org/jira/browse/CASSANDRA-13025
CASSANDRA
(CASSANDRA-13056 test fix was committed and jobs re-run.)
Current release blockers in JIRA on the cassandra-3.11 branch are:
https://issues.apache.org/jira/browse/CASSANDRA-12617
https://issues.apache.org/jira/browse/CASSANDRA-13058
--
Kind regards,
Michael
- All of the unit test variations passed 100% on commit 01cb787.
- CASSANDRA-13056 set as blocker for 3.10 release, if we're pushing for
100% dtest passing. This test is also failing in 3.X and trunk.
- A couple other dtest tests appear to flake on multiple runs on the
cassandra-3.11 branch. Anothe
