[
https://issues.apache.org/jira/browse/CASSANDRA-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-16664:
----------------------------------------
Change Category: Operability
Complexity: Low Hanging Fruit
Fix Version/s: 4.x
4.0.x
Status: Open (was: Triage Needed)
> 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
> Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
