Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Wed, 30 Oct 2013 20:37:27 +0000 (UTC)
From: "Gabriel Reid (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12676670.1383151946206.7480.1383165447307@arcas>
In-Reply-To: <JIRA.12676670.1383151946206@arcas>
References: <JIRA.12676670.1383151946206@arcas>
Subject: [jira] [Commented] (CRUNCH-288) Make it easier to identify the
 failing job in a long pipeline
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CRUNCH-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809584#comment-13809584 ] 

Gabriel Reid commented on CRUNCH-288:
-------------------------------------

+1

> Make it easier to identify the failing job in a long pipeline
> -------------------------------------------------------------
>
>                 Key: CRUNCH-288
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-288
>             Project: Crunch
>          Issue Type: Bug
>            Reporter: Josh Wills
>         Attachments: CRUNCH-288.patch
>
>
> It can be tough to find the ID of an early job that fails in a long pipeline because of all of the debug lines for the failing dependent jobs. This change makes it easier to search through the output logs and find the ID of the root failing job quickly by looking for the string "Job failed!"


--
This message was sent by Atlassian JIRA
(v6.1#6144)