[
https://issues.apache.org/jira/browse/CASSANDRA-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627280#comment-17627280
]
David Capwell commented on CASSANDRA-16664:
-------------------------------------------
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||Jenkins||
|trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-16664-trunk-94CA8A66-AB8A-48E2-803E-60D7AC6FB9A9]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-16664-trunk-94CA8A66-AB8A-48E2-803E-60D7AC6FB9A9]|[build|https://ci-cassandra.apache.org/job/Cassandra-devbranch/2053/]|
> 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.x
>
> 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]
