[ https://issues.apache.org/jira/browse/CASSANDRA-18130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Semb Wever updated CASSANDRA-18130: ------------------------------------------- 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 (was: 5.x) (was: 4.0.x) (was: 4.1.x) > Log hardware and container params during test runs to help troubleshoot > intermittent failures > --------------------------------------------------------------------------------------------- > > Key: CASSANDRA-18130 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18130 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit > Reporter: Josh McKenzie > Assignee: Michael Semb Wever > Priority: Normal > Fix For: 2.2.20, 3.0.31, 3.11.18, 4.0.13, 4.1.5, 5.0-beta2, 5.0, > 5.1 > > > {color:#000000}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]{color} > {color:#000000} {color} > {color:#000000}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.{color} -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org