Cassandra 4.0 Status 2020-12-07

2020-12-07 Thread Jon Meredith
It's been three weeks since the last status update, so here's where we are.

Jira board with 4.0 scope:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661

High level numbers by release phase:

Alpha: 1 (-1 from last update); Last ticket from alpha,
CASSANDRA-13701 lowering default num_tokens in review, related to the
CASSANDRA-16079 Improve dtest runtime.

Beta: 55 (+2 from last update); 31 in-flight, no blockers. 15 tasks
show up in the 7-day stall.

RC: 20 (-6 from last update);

Created vs. resolved continues to trend positively:
https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=filter-12347782&periodName=daily&daysprevious=45&cumulative=true&versionLabels=major&selectedProjectId=12310865&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Acreatedvsresolved-report&atl_token=A5KQ-2QAV-T4JA-FDED_a3bea645259beee42ed00c68f87626d5972705c4_lin&Next=Next


Where you can help:

* Each filter referenced below depends on accurate assignments in
Jira. In addition to actively assigning something you’re working on,
it would also be helpful to review and unassign (both Reviewer and
Assignee) things that you have assigned but may not be able to work on
in the release timeline.

Here’s a query to check that for yourself:

https://issues.apache.org/jira/issues/?filter=12348585&jql=project%20%3D%20cassandra%20AND%20fixversion%20in%20(4.0%2C%204.0.0%2C%204.0-alpha%2C%204.0-beta%2C%204.0-rc%2C%204.0-alpha1%2C%204.0-alpha2%2C%204.0-alpha3%2C%204.0-alpha4%2C%204.0-alpha5%2C%204.0-alpha6%2C%204.0-beta-1%2C%204.0-beta1%2C%204.0-beta2%2C%204.0-beta3%2C%204.0-beta4)%20AND%20(resolution%20%3D%20unresolved%20OR%20status%20!%3D%20resolved)%20and%20(assignee%20%3D%20currentUser()%20or%20reviewer%20%3D%20currentUser()%20or%20reviewers%20%3D%20currentUser())%20

*Needs Reviewer:

1 Beta and 1 RC issues are awaiting review without reviewers.

Timely reviews here obviously keep things flowing, and help by keeping
the changes fresh in the patch contributor’s mind.

https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661&quickFilter=1659

*No assignee:

10 Beta and 4 RC issues

Please take a look and see if it’s within your capacity to take any of these on:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661&quickFilter=1658

*Test analysis and shepherding. We possibly have a fair amount of
unaccounted scope in the Quality/Test tickets that have not been
analyzed and expanded into subtasks.

https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1939

Anything we can do to expedite that will give us a better picture of
what’s left, as well as allow us to parallelize test creation. Good
examples of those that have been broken down are the metrics and
tooling areas:

https://issues.apache.org/jira/browse/CASSANDRA-15582
https://issues.apache.org/jira/browse/CASSANDRA-15583

There are numerous similar tickets remaining.

*Tickets stalled for a week:

1 alpha, 10 beta, 8 GA

https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661&quickFilter=1694


Please let us know on the thread if I have missed anything that needs
attention. I encourage anyone to respond to these reports calling
attention to any localized things that could use it.

As always thanks to everyone for the continued work on the project.

-Jon Meredith

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



Re: cassandra--dtest: module 'pytest' has no attribute 'config'

2020-12-07 Thread Adam Holmberg
Hello. It looks like your environment might be using a newer version of
pytest than is supported by these tests.
https://docs.pytest.org/en/latest/deprecations.html#pytest-config-global

Note that the requirements file specifies a fixed, older version of pytest:
https://github.com/apache/cassandra-dtest/blob/192b70607a0c4a96f524bd5dc0c19c3a28f938f0/requirements.txt#L9

On Fri, Dec 4, 2020 at 5:32 AM Ahmed Eljami  wrote:

> Hi folks,
>
> I'm trying to run dtest on local and getting the following error (I
> configure it to run the only refresh_test.py test):
>
> $ pytest --cassandra-dir=/home/aeljami/workspace/git/cstar/cassandra
>
> == test session
> > starts ==
> > platform linux -- Python 3.6.9, pytest-6.1.2, py-1.9.0, pluggy-0.13.1
> > rootdir: /home/aeljami/workspace/git/cassandra-dtest, configfile:
> > pytest.ini
> > plugins: flaky-3.7.0
> > collected 1 item
> >
> > refresh_test.py E
> > [100%]
> >
> >  ERRORS
> > =
> > __ ERROR at setup of
> > TestRefresh.test_refresh_deadlock_startup
> > __
> >
> > request =  > test_refresh_deadlock_startup>>
> >
> > @pytest.fixture(scope="function", autouse=True)
> > def fixture_logging_setup(request):
> > # set the root logger level to whatever the user asked for
> > # all new loggers created will use the root logger as a template
> > # essentially making this the "default" active log level
> > log_level = logging.INFO
> > try:
> > # first see if logging level overridden by user as command
> > line argument
> > >   log_level_from_option =
> pytest.config.getoption("--log-level")
> > E   AttributeError: module 'pytest' has no attribute 'config'
> >
> > conftest.py:135: AttributeError
> >
>
>  short test summary
> > info 
> > ERROR refresh_test.py::TestRefresh::test_refresh_deadlock_startup -
> > AttributeError: module 'pytest' has no attribute 'config'
> >
>
> $ cat pytest.ini
>
> [pytest]
> > cassandra_dir= /home/aeljami/workspace/git/cstar/cassandra
> > python_files = refresh_test.py
> > junit_suite_name = Cassandra dtests
> > log_print = True
> > log_level = INFO
> > log_format = %(asctime)s,%(msecs)d %(name)s %(levelname)s %(message)s
> > timeout = 900
> >
>
>  Any idea please ?
>
> Thanks
>


-- 
Adam Holmberg
e. adam.holmb...@datastax.com
w. www.datastax.com