[
https://issues.apache.org/jira/browse/CASSANDRA-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16664:
--------------------------------------
Fix Version/s: 4.2
(was: 4.x)
Source Control Link:
https://github.com/apache/cassandra/commit/9a0dd603b18ab5034df27443a4bbc10111edcd8b
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
sorry for the delay, had to track down a failing test issue; it was not related
to this ticket but best to deal with before merging.
> 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.2
>
> Time Spent: 1h
> 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: [email protected]
For additional commands, e-mail: [email protected]
