Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Wed, 13 Jan 2016 00:17:40 +0000 (UTC)
From: "Ewen Cheslack-Postava (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12927148.1451954788000.92131.1452644260001@Atlassian.JIRA>
In-Reply-To: <JIRA.12927148.1451954788000@Atlassian.JIRA>
References: <JIRA.12927148.1451954788000@Atlassian.JIRA>
 <JIRA.12927148.1451954788912@arcas>
Subject: [jira] [Updated] (KAFKA-3063) LogRecoveryTest exits with -1
 occasionally
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/KAFKA-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ewen Cheslack-Postava updated KAFKA-3063:
-----------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Issue resolved by pull request 759
[https://github.com/apache/kafka/pull/759]

> LogRecoveryTest exits with -1 occasionally
> ------------------------------------------
>
>                 Key: KAFKA-3063
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3063
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Guozhang Wang
>            Assignee: Ismael Juma
>             Fix For: 0.9.1.0
>
>
> We see transient failures like the following
> {code}
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':core:test'.
> > Process 'Gradle Test Executor 2' finished with non-zero exit value 1
> {code}
> which are likely to be from an unexpected System.exit(1). But with the current logging settings it is hard to locate which test cases triggered this failures. More investigations needed.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)