[
https://issues.apache.org/jira/browse/CASSANDRA-10471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960618#comment-14960618
]
Sylvain Lebresne commented on CASSANDRA-10471:
----------------------------------------------
bq. I can't tell if the dtests were harmed. There are 20 failures on the
branch. The 3.0 branch hasn't had 20 failures in the past few builds.
I noticed that some dtest build are bad with a lot of tests timeouting (tests
that usually pass). For instance this morning we had a build with [37
failures|http://cassci.datastax.com/job/cassandra-3.0_dtest/261/] (and this
wasn't committed). Anyway, I'm relatively confident the patch doesn't break
anything unrelated as the only code path added are clearly ones that weren't
allowed before, so committed. We can always revert if it surprisingly turns out
that it breaks dtests consistently.
> fix flapping empty_in_test dtest
> --------------------------------
>
> Key: CASSANDRA-10471
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10471
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Jim Witschey
> Assignee: Sylvain Lebresne
> Fix For: 3.0.0 rc2
>
>
> {{upgrade_tests/cql_tests.py:TestCQL.empty_in_test}} fails about half the
> time on the upgrade path from 2.2 to 3.0:
> http://cassci.datastax.com/view/Upgrades/job/storage_engine_upgrade_dtest-22_tarball-30_HEAD/42/testReport/upgrade_tests.cql_tests/TestCQL/empty_in_test/history/
> Once [this dtest PR|https://github.com/riptano/cassandra-dtest/pull/586] is
> merged, these tests should also run with this upgrade path on normal 3.0
> jobs. Until then, you can run it with the following command:
> {code}
> SKIP=false CASSANDRA_VERSION=binary:2.2.0 UPGRADE_TO=git:cassandra-3.0
> nosetests 2>&1 upgrade_tests/cql_tests.py:TestCQL.empty_in_test
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
