[ 
https://issues.apache.org/jira/browse/CASSANDRA-19464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Berenguer Blasi updated CASSANDRA-19464:
----------------------------------------
    Reviewers: Berenguer Blasi

> pytest >= 8.1.0 breaks flaky plugin in cassandra-dtests
> -------------------------------------------------------
>
>                 Key: CASSANDRA-19464
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19464
>             Project: Cassandra
>          Issue Type: Task
>          Components: Test/dtest/python
>            Reporter: Stefan Miklosovic
>            Assignee: Stefan Miklosovic
>            Priority: Normal
>             Fix For: NA
>
>
> I just hit this issue literally today / yesterday. Python's dtests started to 
> fail on some super strange errors like this (1) and similar ... 
> We have "pytest>=6.5.0" in requirements.txt for Python dtests so it seems 
> like it automatically updates to whatever is the latest and it just updated 
> to 8.1.1 and it broke the stuff.
> Some basic investigation yields (2), (3) were complaints are made that it 
> break a lot of things.
> The proper solution seems to be to remove flaky and transition to (4).
> Until we fix this, I think we might just downgrade to the latest 8.0.x 
> pytest, probably this one (5), I am just trying it as I write this.
> (1) 
> https://app.circleci.com/pipelines/github/instaclustr/cassandra/3978/workflows/57f7db32-9892-40bd-9e85-cc9527af7af7/jobs/201511
> (2) https://github.com/pytest-dev/pytest/issues/12066
> (3) https://docs.pytest.org/en/latest/changelog.html#pytest-8-1-0-yanked
> (4) https://github.com/pytest-dev/pytest-rerunfailures
> (5) https://docs.pytest.org/en/latest/changelog.html#pytest-8-0-2-2024-02-24



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to