[prev in list] [next in list] [prev in thread] [next in thread]
List: cassandra-commits
Subject: [jira] [Commented] (CASSANDRA-17912) Fix CircleCI config for running Python upgrade tests on 3.0 and
From: "Ekaterina Dimitrova (Jira)" <jira () apache ! org>
Date: 2022-09-30 21:52:00
Message-ID: JIRA.13482611.1663773421000.354567.1664574720006 () Atlassian ! JIRA
[Download RAW message or body]
[ https://issues.apache.org/jira/browse/CASSANDRA-17912?page=com.atlassian.jira.pl \
ugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17611779#comment-17611779 \
]
Ekaterina Dimitrova commented on CASSANDRA-17912:
-------------------------------------------------
So I pushed that change to 3.0 and 3.11 but still something doesn't click.
If we look in butler there are two tests consistently failing that I cannot find in \
the CircleCI artifacts.
Then I check number of tests by looking into [this Jenkins table of \
results|https://jenkins-cm4.apache.org/job/Cassandra-3.0/296/testReport/] which lists \
some numbers I sum up and the Circle numbers and they also don't click...
Something fishy is going on... I will keep on looking
> 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/testR \
> eport/junit/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upg \
> rade_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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic