[
https://issues.apache.org/jira/browse/CASSANDRA-17912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629010#comment-17629010
]
Ekaterina Dimitrova edited comment on CASSANDRA-17912 at 11/4/22 2:21 PM:
--------------------------------------------------------------------------
Thanks [~mck] !
{quote}my only comment was the collapsing of multiple lines in the yaml to one
long line. one line makes it hard to read and to review changes.
{quote}
I am sorry, I forgot to post on the ticket earlier - the collapse happens when
we use the CircleCI cli tool to create our configuration from config-2_1.yml. I
opened a support ticket for them and the explanation was that they rely on
third-party package which is to be blamed for the collapse... This response was
not rely satisfying, considering we use paid accounts and this configuration is
the primary point to configure their product. They will continue looking on
what they can do but from my experience, it will take some time.
Agreed with [~mck] offline to commit the patch now and hopefully the collapse
will be solved later, I will follow up with CircleCI support teams.
{quote}one line makes it hard to read and to review changes.
{quote}
Agreed, also for maintenance. That's why I raised the support ticket but with
no good luck so far.
Starting commit soon
was (Author: e.dimitrova):
Thanks [~mck] !
{quote}my only comment was the collapsing of multiple lines in the yaml to one
long line. one line makes it hard to read and to review changes.
{quote}
I am sorry, I forgot to post on the ticket earlier - the collapse happens when
we use the CircleCI cli. I opened a support ticket for them and the explanation
was that they rely on third-party package which is to be blamed for the
collapse... This response was not rely satisfying, considering we use paid
accounts and this configuration is the primary point to configure their
product. They will continue looking on what they can do but from my experience,
it will take some time.
Agreed with [~mck] offline to commit the patch now and hopefully the collapse
will be solved later, I will follow up with CircleCI support teams.
{quote}one line makes it hard to read and to review changes.
{quote}
Agreed, also for maintenance. That's why I raised the support ticket but with
no good luck so far.
Starting commit soon
> Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11
> --------------------------------------------------------------------
>
> Key: CASSANDRA-17912
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17912
> Project: Cassandra
> Issue Type: Bug
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 3.0.x, 3.11.x
>
>
> It was noticed that Circle CI pushes to run irrelevant for 3.0 and 3.11
> Python upgrade tests. Those are properly skipped in Jenkins.
> Example runs:
> [CircleCI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1931/workflows/39ef5261-a6bf-4e77-a412-e750e322a231/jobs/15293]
> - 3.0 run
> [Jenkins|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/]
> - while typing this I actually noticed [one
> test|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/testReport/junit/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_parallel_upgrade_with_internode_ssl/]
> only looking suspicious in Jenkins as it ends the upgrade in 3.11 when we
> test 3.0...
> This is good to be fixed for two reasons - reduce the noise so we do not miss
> legit failures and we should not spend resources to try to run those tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
