[
https://issues.apache.org/jira/browse/CASSANDRA-11465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397244#comment-15397244
]
Stefania commented on CASSANDRA-11465:
--------------------------------------
Thanks for restarting the tests.
There are a number of failures, all accounted for except for
[this|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11465-3.0-dtest/lastCompletedBuild/testReport/snapshot_test/TestArchiveCommitlog/test_archive_commitlog]
in 3.0 and
[this|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11465-3.9-dtest/lastCompletedBuild/testReport/delete_insert_test/DeleteInsertTest/delete_insert_search_test/]
in 3.9.
I'm not sure they are related given that both commitlog and secondary indexes
are local, but 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}}?
> 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)
