[jira] [Updated] (CASSANDRA-16664) Log JVM Arguments at in-JVM Test Class Initialization

["Natnael Adere (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Natnael Adere updated CASSANDRA-16664:
--------------------------------------
    Test and Documentation Plan: Testing was done with CircleCI 
                         Status: Patch Available  (was: In Progress)

Patch: [https://github.com/apache/cassandra/pull/1938/files]

Circle CI: [https://app.circleci.com/pipelines/github/NateAdere/cassandra?branch=Cassandra-16664-trunk]

 

> Log JVM Arguments at in-JVM Test Class Initialization
> -----------------------------------------------------
>
>                 Key: CASSANDRA-16664
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16664
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Test/dtest/java
>            Reporter: Caleb Rackliffe
>            Assignee: Natnael Adere
>            Priority: Normal
>              Labels: ghc-lhf, lhf
>             Fix For: 4.0.x, 4.x
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Normal C* startup flows through {{CassandraDaemon.setup()}}, which calls {{logSystemInfo()}}, logging JVM arguments and a number of other useful bits of information. The in-JVM dtest startup does not flow through {{CassandraDaemon.setup()}}, and therefore does not. It would be useful for troubleshooting purposes if {{TestBaseImpl}} logged the JVM arguments before moving into executing tests.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org