[CASSANDRA-18130] Log hardware and container params during test runs to help troubleshoot intermittent failures

• Type: Task
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.20, 3.0.31, 3.11.18, 4.0.13, 4.1.5, 5.0-beta2, 5.0, 5.1
• Component/s: Test/dtest/java, Test/dtest/python, Test/unit
• Epic Link: repeatable_ci-cassandra
• Change Category: Quality Assurance
• Complexity: Normal
• Platform: All

Test and Documentation Plan

CI (manual paste of jenkinsfile in replay action)

• Assignee: Michael Semb Wever
• Reporter: Josh McKenzie

Authors

Josh McKenzie, Michael Semb Wever

Reviewers

Josh McKenzie

• Created: 03/Jan/23 18:55
• Updated: Yesterday 19:57
• Resolved: Yesterday 19:56

Description

We’ve long had flakiness in our containerized ASF CI environment that we don’t see in circleci. The environment itself is both containerized and heterogenous, so there are differences in both the hardware environment and the software environment in which it executes. For reference, see: https://github.com/apache/cassandra-builds/blob/trunk/ASF-jenkins-agents.md#current-agents
 
We should log a variety of hardware, container, and software environment details to help get to the bottom of where some test failures may be occurring. As we don’t have shell access to the machines it’ll be easier to have this information logged / retrieved during test runs than to try and profile each host independently.

Issue Links

• is fixed by: CASSANDRA-19558 Standalone jenkinsfile first round bug fixes