[
https://issues.apache.org/jira/browse/CASSANDRA-18130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17656983#comment-17656983
]
Michael Semb Wever commented on CASSANDRA-18130:
------------------------------------------------
bq. I believe you have an env up and running we might be able to check this on
for Michael Semb Wever ?
Yes, but it's not big enough to handle a pipeline build. Let me loop back on
this later in the week, ok?
> 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: Josh McKenzie
> Priority: Normal
>
> {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
