[
https://issues.apache.org/jira/browse/CASSANDRA-11465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398441#comment-15398441
]
Paulo Motta commented on CASSANDRA-11465:
-----------------------------------------
bq. There are a number of failures, all accounted for except for this in 3.0
and this in 3.9.
{{snapshot_test.TestArchiveCommitlog.test_archive_commitlog}} is being
addressed on CASSANDRA-11811 but {{delete_insert_search_test}} in fact looks
like a new failure, but it seems unrelated.
bq. perhaps to be on the safe side we should set the default value of
WAIT_FOR_PENDING_EVENTS_TIMEOUT_SECS to zero rather than 1 second so that this
patch only affects the tests that set
-Dcassandra.wait_for_tracing_events_timeout_secs?
I think we can keep it, since this issue may also happen in ordinary tracing
sessions so it may help to make this a bit more robust and AFAIK tracing is
only used for debugging/troubleshooting so it's not particularly critical. In
any case, I submitted an additional [3.9 dtest
run|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11465-3.9-dtest/4/]
to verify the previous failures were indeed unrelated.
I will mark as ready to commit if this last test run looks good. Thanks!
> dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-11465
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11465
> Project: Cassandra
> Issue Type: Bug
> Reporter: Philip Thompson
> Assignee: Stefania
> Labels: dtest
>
> Failing on the following assert, on trunk only:
> {{self.assertEqual(len(errs[0]), 1)}}
> Is not failing consistently.
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1087/testReport/cql_tracing_test/TestCqlTracing/tracing_unknown_impl_test
> Failed on CassCI build trunk_dtest #1087
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
