[
https://issues.apache.org/jira/browse/CASSANDRA-17893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17604822#comment-17604822
]
Josh McKenzie commented on CASSANDRA-17893:
-------------------------------------------
Can we infer that from just the timeout rate?
For example - if the test is running near the timeout limit and gets a bad roll
of the dice w/neighbors and gets pushed over the edge, is that an environmental
flake or a test that needs tuning?
> Test Failure:
> dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestUpgrade_indev_4_1_x_To_indev_trunk.test_parallel_upgrade
>
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17893
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17893
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
> Reporter: Josh McKenzie
> Priority: Normal
> Fix For: 4.1.x, 4.x
>
>
> Link to failure:
> https://ci-cassandra.apache.org/job/Cassandra-4.1/162/testReport/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestUpgrade_indev_4_1_x_To_indev_trunk/test_parallel_upgrade/
> Error Message
> Failed: Timeout >900.0s
> Stack Trace
> {code}
> else:
> # wait for the situation to clarify, either stop or just
> a pause in log production
> > time.sleep(1)
> E Failed: Timeout >900.0s
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
