[
https://issues.apache.org/jira/browse/CASSANDRA-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064019#comment-17064019
]
David Capwell commented on CASSANDRA-15649:
-------------------------------------------
sorry, talked to [~djoshi] about that. looks like when python3 was added LOWER
and HIGHER were updated, but config.yml was not replaced with config.yml.LOWER
(undocumented, something you have to do though).
Since I changed the build, I had to update config.yml to pick that up (cp
config.yml.LOWER config.yml)
bq. (And I can't access the CircleCI links…?)
-_- that isn't good... ill try to figure out why Monday.
> test.distributed.timeout no longer respected in CircleCI
> --------------------------------------------------------
>
> Key: CASSANDRA-15649
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15649
> Project: Cassandra
> Issue Type: Bug
> Components: Build
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> After switching jvm dtest over testclasslist (CASSANDRA-15508) we no longer
> respect the dtest timeout and instead use the unit test timeout (4m vs 6m).
> This does not impact Jenkins as I made sure to check that before calling
> testclasslist; though this does impact 2.2, 3.0, and 3.11 as well.
> ||Config||Trunk||3.11||3.0||2.2||
> |LOWER||[Circle
> CI|https://circleci.com/workflow-run/04f7fbe2-1919-4da0-bf72-ba41b41c3072]|
> TBD | TBD | TBD |
> |HIGHER| [Circle
> CI|https://circleci.com/workflow-run/036bbad1-541a-49dc-a567-cef2300fa847] |
> TBD | TBD | TBD |
> CI Failures were flaky tests, below are their links
> * CASSANDRA-15630
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
