You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2022/10/21 19:57:00 UTC
[jira] [Commented] (CASSANDRA-16664) Log JVM Arguments at in-JVM Test Class Initialization
[ https://issues.apache.org/jira/browse/CASSANDRA-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622461#comment-17622461 ]
David Capwell commented on CASSANDRA-16664:
-------------------------------------------
[~maedhroz] as the reporter would you mind reviewing as well?
> 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: 20m
> 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