You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Gwen Shapira (JIRA)" <ji...@apache.org> on 2014/08/26 02:02:57 UTC
[jira] [Updated] (KAFKA-1611) Improve system test configuration
[ https://issues.apache.org/jira/browse/KAFKA-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gwen Shapira updated KAFKA-1611:
--------------------------------
Attachment: KAFKA-1611.0.patch
Fixed the hardcoded java_home issue and added support for JAVA_HOME environment variable.
Did not filter the remote host validation based on which testsuites will run - seemed like too much extra complexity for too little payoff.
> Improve system test configuration
> ---------------------------------
>
> Key: KAFKA-1611
> URL: https://issues.apache.org/jira/browse/KAFKA-1611
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Gwen Shapira
> Assignee: Gwen Shapira
> Fix For: 0.9.0
>
> Attachments: KAFKA-1611.0.patch
>
>
> I'd like to make the config a bit more "out of the box" for the common case of local cluster. This will include:
> 1. Fix cluster_config.json of migration testsuite, it has hardcoded path that prevents it from working out of the box at all.
> 2. Use JAVA_HOME environment variable if "default" is specified and if JAVA_HOME is defined. The current guessing method is a bit broken and using JAVA_HOME will allow devs to configure their default java dir without editing multiple cluster_config.json files in multiple places.
> 3. (if feasible without too much headache): Configure remote hosts only for test packages that will not be skipped. This will reduce some overhead in the common use cases.
--
This message was sent by Atlassian JIRA
(v6.2#6252)