[ 
https://issues.apache.org/jira/browse/CASSANDRA-17140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454918#comment-17454918
 ] 

Ekaterina Dimitrova edited comment on CASSANDRA-17140 at 12/8/21, 1:23 AM:
---------------------------------------------------------------------------

[~Bereng] , as mentioned on CASSANDRA-15252 I didn't know you are looking 
already into this ticket so I was also bisecting today.

Now rolling upgrades are failing on 3.0, 3.11, 4.0 and trunk. 

While I agree on the date - 1st October when they started failing, I don't 
think it is because of CASSANDRA-15252.

I was not able to run the tests locally, getting different error, something 
with my python that I am not able to fix yet...

But I was digging into Jenkins, as I mentioned on the other ticket, and I found 
rolling upgrades not failing on 3.0 with CASSANDRA-16795, but failing with 

CASSANDRA-17014 on both 3.0 and 3.11. Please check 
[here|https://ci-cassandra.apache.org/job/Cassandra-3.0/204/].  for 3.0 and 
also failing in Jenkins for 3.11 
[here|https://jenkins-cm4.apache.org/job/Cassandra-3.11/265/#showFailuresLink]

If it is not CASSANDRA-17014, then there are only two other options possible 
after CASSANDRA-16795 - 

CASSANDRA-16959 or CASSANDRA-14612.

 


was (Author: e.dimitrova):
[~Bereng] , as mentioned on CASSANDRA-15252 I didn't know you are looking 
already into this ticket so I was also bisecting today.

Now rolling upgrades are failing on 3.0, 3.11, 4.0 and trunk. 

While I agree on the date - 1st October when they started failing, I don't 
think it is because of CASSANDRA-15252.

I was not able to run the tests locally, getting different error, something 
with my python that I am not able to fix yet...

But I was digging into Jenkins, as I mentioned on the other ticket, and I found 
rolling upgrades not failing on 3.0 with CASSANDRA-16795, but failing with 

CASSANDRA-17014 on both 3.0 and 3.11.

If it is not CASSANDRA-17014, then there are only two other options possible 
after CASSANDRA-16795 - 

CASSANDRA-16959 or CASSANDRA-14612.

 

> Broken test_rolling_upgrade - 
> upgrade_tests.upgrade_through_versions_test.TestUpgrade_indev_3_0_x_To_indev_4_0_x
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17140
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17140
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CI
>            Reporter: Yifan Cai
>            Priority: Normal
>             Fix For: 4.0.x
>
>
> The tests "test_rolling_upgrade" fail with the below error. 
>  
> [https://app.circleci.com/pipelines/github/yifan-c/cassandra/279/workflows/6340cd42-0b27-42c2-8418-9f8b56c57bea/jobs/1990]
>  
> I am able to alway produce it by running the test locally too. 
> {{$ pytest --execute-upgrade-tests-only --upgrade-target-version-only 
> --upgrade-version-selection all --cassandra-version=4.0 
> upgrade_tests/upgrade_through_versions_test.py::TestUpgrade_indev_3_11_x_To_indev_4_0_x::test_rolling_upgrade}}
>  
> {code:java}
> self = 
> <upgrade_tests.upgrade_through_versions_test.TestUpgrade_indev_3_0_x_To_indev_4_0_x
>  object at 0x7ffba4242fd0>
> subprocs = [<Process(Process-1, stopped[SIGKILL] daemon)>, 
> <Process(Process-2, stopped[1] daemon)>]
>     def _check_on_subprocs(self, subprocs):
>         """
>             Check on given subprocesses.
>     
>             If any are not alive, we'll go ahead and terminate any remaining 
> alive subprocesses since this test is going to fail.
>             """
>         subproc_statuses = [s.is_alive() for s in subprocs]
>         if not all(subproc_statuses):
>             message = "A subprocess has terminated early. Subprocess 
> statuses: "
>             for s in subprocs:
>                 message += "{name} (is_alive: {aliveness}), 
> ".format(name=s.name, aliveness=s.is_alive())
>             message += "attempting to terminate remaining subprocesses now."
>             self._terminate_subprocs()
> >           raise RuntimeError(message)
> E           RuntimeError: A subprocess has terminated early. Subprocess 
> statuses: Process-1 (is_alive: True), Process-2 (is_alive: False), attempting 
> to terminate remaining subprocesses now.{code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to