[
https://issues.apache.org/jira/browse/CASSANDRA-16853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17398630#comment-17398630
]
Michael Semb Wever commented on CASSANDRA-16853:
------------------------------------------------
It is only about code style, and it would have been nice to get the repo
cleaned up. I had started on doing that
[here|https://github.com/thelastpickle/cassandra-dtest/tree/mck/fix-codestyle-violations]
but stalled on the effort.
It would be nice to just reduce the violations checked so that it passes for
now, so to keep an existing degree of code style in place. But I have no
objections to removing it altogether either.
> CircleCI folder in dtest is confusing
> -------------------------------------
>
> Key: CASSANDRA-16853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16853
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
> Reporter: Ruslan Fomkin
> Priority: Normal
>
> I made a patch to dtest without affecting Cassandra. cassandra-dtest repo
> contains folder with CircleCI configuration file. So I tried to run a [build
> from
> CircleCI|https://app.circleci.com/pipelines/github/k-rus/cassandra-dtest/3/workflows/6ea8058d-37b0-40e8-89be-d9b4afdf279c/jobs/4]
> and it failed with an error related to configuration:
> {code:java}
> ERROR: flake8 3.9.2 has requirement pycodestyle<2.8.0,>=2.7.0, but you'll
> have pycodestyle 2.3.1 which is incompatible.
> {code}
> The CircleCI config contains
> {code:java}
> sudo pip install pycodestyle==2.3.1 flake8
> {code}
> , so it should lead to the error.
> From the discussion in community I learned that dtest are run as part of
> Cassandra build and not on cassandra-dtest directly. Is the config in dtest
> maintained? If not, it might be good to remove. Or may be add some comment
> about it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
