Return-Path: X-Original-To: apmail-builds-archive@minotaur.apache.org Delivered-To: apmail-builds-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B94F018D08 for ; Sun, 5 Jul 2015 20:56:16 +0000 (UTC) Received: (qmail 39917 invoked by uid 500); 5 Jul 2015 20:56:16 -0000 Delivered-To: apmail-builds-archive@apache.org Received: (qmail 39843 invoked by uid 500); 5 Jul 2015 20:56:16 -0000 Mailing-List: contact builds-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: builds@apache.org Delivered-To: mailing list builds@apache.org Delivered-To: moderator for builds@apache.org Received: (qmail 14366 invoked by uid 99); 5 Jul 2015 16:00:19 -0000 X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.98 X-Spam-Level: *** X-Spam-Status: No, score=3.98 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4JUpzqMziBJ+MmSe3j1NDnP4G4LzF0i+t3z1IicfgH0=; b=aWMHS7YcbWCggzFc/2Xq/mcsr0i9ssg953wQQIZEay0/VgQ/XoNlxQR6bcjDiLoxeE Ax3DYHUqrPz4K5OjxoYyaYOaSk7kvGbSrnyb+YBiKkka56oJkQXiIGOlDkRBWE3jGxTM kqyBLs49nOephIFcyOrjbaVB201vJJtF+6uXBqXg27zRgyjpSnkh1Njsct9tNmdUYTO4 mnXPN4y+blcwGh2avSgxrhkM6L8UBzDjprBTLakh1RUK1o8iLhLhd5Jgkp1I0fl5zzP4 Cf/lb6euJQllxb5PzRecj08P9oXJlUMmJvKg/XXHUS7WE0/l1vUyyTsz344LT9HF7TEO lP0Q== X-Gm-Message-State: ALoCoQn9F21BhMw/uxUZAxByk5z5VwHBRWFbnfqgcAlFxETNWkuBDe17QgF8jcULIllZTtPcmFhn MIME-Version: 1.0 X-Received: by 10.42.30.208 with SMTP id w16mr30256947icc.88.1436112011130; Sun, 05 Jul 2015 09:00:11 -0700 (PDT) In-Reply-To: References: Date: Sun, 5 Jul 2015 12:00:11 -0400 Message-ID: Subject: Fwd: Need help with info for a Nutch failure occurring on Jenkins From: Pete Ciuffetti To: builds@apache.org Cc: dev@nutch.apache.org Content-Type: multipart/alternative; boundary=20cf3042727a4816ad051a22e2f5 --20cf3042727a4816ad051a22e2f5 Content-Type: text/plain; charset=UTF-8 Hello: I'm investigating a sporadic Nutch unit test failure described here: https://issues.apache.org/jira/browse/NUTCH-2059 Unfortunately neither I nor the other person Im working with (Chris Mattmann) are able to reproduce this failure on our sandboxes. It only occurs sporadically on Jenkins. When it fails, the jenkins log only reports that there is an error, but not any details about the error. https://builds.apache.org/view/All/job/Nutch-trunk/3192/consoleFull Would it be possible for a Jenkins admin to provide a copy of the test output file from a recent failure? Building remotely on jenkins-ubuntu-1404-4gb-302 (jenkins-cloud-4GB cloud-slave Ubuntu ubuntu) in workspace /jenkins/workspace/Nutch-trunk The file Im looking for is... /jenkins/workspace/Nutch-trunk/trunk/build/test/build/protocol-httpclient/test/TEST-org.apache.nutch.protocol.httpclient.TestProtocolHttpClient.txt Thanks Pete Ciuffetti --20cf3042727a4816ad051a22e2f5--