av9ash/GitBugs huggingface dataset:
Bug: Fix test failures when running via IntelliJ
Status: Resolved
Priority: Low
Resolution: Fixed
Created: 15/Jun/21 19:33
Resolved: 16/Jun/21 19:34

After running `ant generate-idea-files` and opening the project in IntelliJ IDEA 2021.1.2, tests that referenced PropertyFileSnitch (like NetworkTopologyStrategyTest.testProperties) failed with error org.apache.cassandra.exceptions.ConfigurationException: Unable to read cassandra-topology.properties.

 

I fixed this issue in IntelliJ by marking test/conf as Test Resources (under Project Structure), and have patches to fix `ant generate-idea-files` so the manual reconfiguration is not necessary:

 

3.0 - [https://github.com/aratno/cassandra/tree/abe-fix-intellij-test-3-0]
Bug: Add a microbenchmark for checksum calculation
Status: Resolved
Priority: Low
Resolution: Fixed
Created: 30/Apr/21 11:50
Resolved: 30/Apr/21 14:08

h2. Overview

As a part CASSANDRA-16360 there was a need to change the checksum algo from _CRC32_ to _CRC32C_ for client/internode messaging. Before making that change it would be nice to have a way to measure performance for checksum calculation (similarly to {{HashingBench}} for hash calculation).

In fact, the microbenchmark has been already created as a part of that ticket. However, after running it I saw a performance degradation for Java 8. After a discussion among the community, it was decided to wait with _CRC32C_ until Java 8 support is abandoned. The purpose of this ticket is to merge the benchmark changes separately.

h2. What needs to be done
 * Create a microbenchmark

h2. Link to PR
[https://github.com/apache/cassandra/pull/951/files]
Bug: Remove references to run_dtests from README
Status: Resolved
Priority: Low
Resolution: Fixed
Created: 21/Apr/21 14:45
Resolved: 22/Apr/21 18:44

Newcomers to cassandra-dtest that look through README.md will see that the run_dtests.py script is the quickest way to get started running tests. Unfortunately, the script has a number of problems and I'm not sure it ever work properly after the move to the pytest framework.
h2. Process stdout/stderr buffering

Firstly, when I execute run_dtests.py I don't see any output after

{{$ ./run_dtests.py --dtest-tests paging_test.py }}
{{============================= test session starts ==============================}}

This looks likely to be because of the buffering that pytest does internally for stdout and stderr and because of the way that it's executed by run_dtests.py, i.e. I suspect that run_dtests.py is blocked on the following line for most of the execution because there's no data available in the pipe for stderr:

{{stderr_output = sp.stderr.readline()}}

See also [https://github.com/pytest-dev/pytest/issues/1886]
h2. --pytest-options doesn't work

Secondly, the options specified in --pytest-options aren't actually passed through to pytest.
h2. Most devs run pytest directly

When I spoke to [~edimitrova] it seemed like most developers just run the tests directly with pytest which would explain why run_dtests.py has bitrotted.