[
https://issues.apache.org/jira/browse/CASSANDRA-18391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707245#comment-17707245
]
Andres de la Peña commented on CASSANDRA-18391:
-----------------------------------------------
Looks good to me. I have verified that the test is still run in
[3.0|https://app.circleci.com/pipelines/github/adelapena/cassandra/2741/workflows/40dcb79f-5178-4736-ba16-bd62ac486870/jobs/32976/artifacts]
and
[3.11|https://app.circleci.com/pipelines/github/adelapena/cassandra/2740/workflows/a7fa29c9-6b4f-4628-8e89-ebde92b930ac/jobs/32977/artifacts].
Hopefully skipping the ccm setup will help with other timeouts.
Probably we should add a similar skipping of the ccm setup on
{{ported_to_in_jvm}}, a few lines below,
[here|https://github.com/driftx/cassandra-dtest/blob/4481f86e80f9625bcb1cfc36e1a97028d235b1d0/conftest.py#L493].
> consistent timeout:
> dtest-upgrade.upgrade_tests.cql_tests.cls.test_cql3_non_compound_range_tombstones
> on trunk
> --------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18391
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18391
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
> Reporter: Josh McKenzie
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 5.x
>
>
> Failed 30 times in the last 30 runs. Flakiness: 0%, Stability: 0%
> link:
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1511/testReport/dtest-upgrade.upgrade_tests.cql_tests/cls/test_cql3_non_compound_range_tombstones/
> Error message: failed on setup with "Failed: Timeout >900.0s"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
