[CASSANDRA-16399] Selecting resource intensive tests is not consistent

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.20, 3.0.24, 3.11.10, 4.0-rc1, 4.0
• Component/s: Test/dtest/python
• Epic Link: 40_Quality_Test
• Bug Category: Code - Bug - Unclear Impact
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: Adhoc Test
• Platform: All
• Since Version: NA

Source Control Link

https://github.com/apache/cassandra-dtest/commit/ec84618b7450ef9357a3a88fc93e39d74a34b02e

Test and Documentation Plan

Manual testing, plus ci-cassandra.a.o

• Assignee: Jacek Lewandowski
• Reporter: Jacek Lewandowski

Authors

Jacek Lewandowski

Reviewers

Michael Semb Wever, Tomasz Lasica

• Created: 22/Jan/21 07:52
• Updated: 28/Jan/21 11:03
• Resolved: 28/Jan/21 11:03

Description

It looks like there are two problems:

• collection of tests to run fails when there are log messages in stderr
• collection of resource intensive tests (with

  --only-resource-intensive-tests

  ) is broken

 

Issue Links

• blocks: CASSANDRA-16221 Jenkins doesn't run high resource python dtests with novonode so missing some tests
• links to: PR #115