[
https://issues.apache.org/jira/browse/CASSANDRA-11928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961764#comment-16961764
]
Michael Semb Wever edited comment on CASSANDRA-11928 at 10/29/19 7:40 AM:
--------------------------------------------------------------------------
I've been able to reproduce the flakiness of the dtest along all of trunk since
the {{cassandra-3.11}} was branched. This corresponds to the date of when this
ticket was reported. Oddly though, we don't see the flakiness in ASF Jenkins
anywhere except for against trunk. This could be because Cassandra 4.0 uses
more resources per node than previous versions (getting a three node ccm
working reliably in tests in circleci/travis/jenkens is considerably harder
than it was in Cassandra 3.11 and before).
The bisecting i did used the following {{bisect.sh}} script and recipe.
The {{bisect.sh}} script:
{noformat}
#!/bin/bash
set -e
cd /home/mick/src/apache/cassandra
ant realclean
ant artifacts
cd /home/mick/src/apache/cassandra-dtest/
source ~/dtest/bin/activate
# iterate 20 times, making sure this flakey test works on this sha
for i in {0..19} ; do
echo " ITERATION $i "
python -m pytest --cassandra-dir=/home/mick/src/apache/cassandra
cql_tracing_test.py
done
cd /home/mick/src/apache/cassandra
git stash
{noformat}
The execution:
{code}
git bisect start
git bisect bad
git bisect good `git log cassandra-3.11..trunk --oneline | tail -1 | cut -d' '
-f1`
git bisect run ./bisect.sh
{code}
was (Author: michaelsembwever):
I've been able to reproduce the flakiness of the dtest along all of the trunk
since the {{cassandra-3.11}} was branched. This corresponds to the date of when
this ticket was reported. Oddly though, we don't see the flakiness in ASF
Jenkins anywhere except for against trunk. This could be because Cassandra 4.0
uses more resources per node than previous versions (getting a three node ccm
working reliably in tests in circleci/travis/jenkens is considerably harder
than it was in Cassandra 3.11 and before).
The bisecting i did used the following {{bisect.sh}} script and recipe.
The {{bisect.sh}} script:
{noformat}
#!/bin/bash
set -e
cd /home/mick/src/apache/cassandra
ant realclean
ant artifacts
cd /home/mick/src/apache/cassandra-dtest/
source ~/dtest/bin/activate
# iterate 20 times, making sure this flakey test works on this sha
for i in {0..19} ; do
echo " ITERATION $i "
python -m pytest --cassandra-dir=/home/mick/src/apache/cassandra
cql_tracing_test.py
done
cd /home/mick/src/apache/cassandra
git stash
{noformat}
The execution:
{code}
git bisect start
git bisect bad
git bisect good `git log cassandra-3.11..trunk --oneline | tail -1 | cut -d' '
-f1`
git bisect run ./bisect.sh
{code}
> dtest failure in cql_tracing_test.TestCqlTracing.tracing_simple_test
> --------------------------------------------------------------------
>
> Key: CASSANDRA-11928
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11928
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
> Reporter: Craig Kodman
> Priority: Normal
> Labels: dtest, flaky
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/727/testReport/cql_tracing_test/TestCqlTracing/tracing_simple_test
> Failed on CassCI build cassandra-3.0_dtest #727
> Is it a problem that the tracing message with the query is missing?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
