You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Michael Shuler <mi...@pbandjelly.org> on 2016/12/19 18:08:32 UTC
3.10 release status: blocked on dtest
- 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. Another set of re-runs triggered.
http://cassci.datastax.com/view/cassandra-3.11/
If we're shooting for 100% tests passing before allowing a release to go
up for vote, let's attack the test-failure label in JIRA!:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20labels%20%3D%20test-failure%20AND%20resolution%20%3D%20Unresolved
--
Kind regards,
Michael
Re: 3.10 release status: blocked on dtest
Posted by Ariel Weisberg <ar...@weisberg.ws>.
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 offheap_dtest which all have a few failing tests. I
think we should consider those as blockers as well.
The upgrade tests have this chicken and egg issue where they test the
previous current release against the in development release and if there
is a bug preventing upgrade you end up with a lot of failing tests that
continue to fail even after the bug is fixed.
There is a also a real bug fixed by
https://github.com/apache/cassandra/commit/c612cd8d7dbd24888c216ad53f974686b88dd601
that near as I can tell isn't included in 3.10. It will continue to fail
until we release a version that addresses the issue. It kind of makes
you think that if the current version fails, but the in development
version passes we want a quick way of filtering out the failure.
I also found an issue with max version in the since decorator that
causes some of the upgrade tests to fail. I gave the fix for that to
Philip.
I haven't managed to get the upgrade tests passing after addressing the
above two issues, but it's always hard to tell what is my environment
and what is the tests.
Ariel
On Wed, Jan 4, 2017, at 01:46 PM, Michael Shuler wrote:
> 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 <mi...@pbandjelly.org>
> > 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.apache.org/jira/browse/CASSANDRA-12617
> >>> https://issues.apache.org/jira/browse/CASSANDRA-13058
> >>
> >> and https://issues.apache.org/jira/browse/CASSANDRA-13025
> >>
> >> CASSANDRA-13058 is unassigned, but was just updated (thanks Stefan!).
> >> The other tickets are assigned, but have not been updated in a while.
> >>
> >> JQL for 3.10:
> >>
> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%203.10%20AND%20resolution%20%3D%20Unresolved
> >>
> >> --
> >> Kind regards,
> >> Michael
> >>
>
Re: 3.10 release status: blocked on dtest
Posted by Michael Shuler <mi...@pbandjelly.org>.
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 <mi...@pbandjelly.org>
> 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.apache.org/jira/browse/CASSANDRA-12617
>>> https://issues.apache.org/jira/browse/CASSANDRA-13058
>>
>> and https://issues.apache.org/jira/browse/CASSANDRA-13025
>>
>> CASSANDRA-13058 is unassigned, but was just updated (thanks Stefan!).
>> The other tickets are assigned, but have not been updated in a while.
>>
>> JQL for 3.10:
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%203.10%20AND%20resolution%20%3D%20Unresolved
>>
>> --
>> Kind regards,
>> Michael
>>
Re: 3.10 release status: blocked on dtest
Posted by Oleksandr Petrov <ol...@gmail.com>.
#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 <mi...@pbandjelly.org>
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.apache.org/jira/browse/CASSANDRA-12617
> > https://issues.apache.org/jira/browse/CASSANDRA-13058
>
> and https://issues.apache.org/jira/browse/CASSANDRA-13025
>
> CASSANDRA-13058 is unassigned, but was just updated (thanks Stefan!).
> The other tickets are assigned, but have not been updated in a while.
>
> JQL for 3.10:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%203.10%20AND%20resolution%20%3D%20Unresolved
>
> --
> Kind regards,
> Michael
>
--
Alex Petrov
Re: 3.10 release status: blocked on dtest
Posted by Michael Shuler <mi...@pbandjelly.org>.
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-13058 is unassigned, but was just updated (thanks Stefan!).
The other tickets are assigned, but have not been updated in a while.
JQL for 3.10:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%203.10%20AND%20resolution%20%3D%20Unresolved
--
Kind regards,
Michael
Re: 3.10 release status: blocked on dtest
Posted by Michael Shuler <mi...@pbandjelly.org>.
(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