[
https://issues.apache.org/jira/browse/CASSANDRA-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185603#comment-17185603
]
Berenguer Blasi edited comment on CASSANDRA-16073 at 8/27/20, 5:37 AM:
-----------------------------------------------------------------------
Seems latest jenkins run spike to 50-ish failures. This is strange as the dtest
runs pre-merge where clean.
I have pushed a new [PR|https://github.com/apache/cassandra-dtest/pull/92] to
revert the generic timeout change in favor of a specific test fix. -I will need
sbdy to fire a dtest ci for me...-
Edit: Waiting on CI
was (Author: bereng):
Seems latest jenkins run spike to 50-ish failures. This is strange as the dtest
runs pre-merge where clean.
I have pushed a new [PR|https://github.com/apache/cassandra-dtest/pull/92] to
revert the generic timeout change in favor of a specific test fix. I will need
sbdy to fire a dtest ci for me...
> cql_tracing_test.py failing repeatedly on jenkins
> -------------------------------------------------
>
> Key: CASSANDRA-16073
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16073
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
> Reporter: Berenguer Blasi
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 4.0-beta
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Jenkins has been failing tracing tests repeatedly
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
