From notifications-return-7926-archive-asf-public=cust-asf.ponee.io@yetus.apache.org Mon Aug 19 16:11:03 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id B3393180669 for ; Mon, 19 Aug 2019 18:11:02 +0200 (CEST) Received: (qmail 91853 invoked by uid 500); 19 Aug 2019 16:11:02 -0000 Mailing-List: contact notifications-help@yetus.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@yetus.apache.org Delivered-To: mailing list notifications@yetus.apache.org Received: (qmail 91844 invoked by uid 99); 19 Aug 2019 16:11:02 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Aug 2019 16:11:02 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 8C7EFE300B for ; Mon, 19 Aug 2019 16:11:01 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 49213782232 for ; Mon, 19 Aug 2019 16:11:00 +0000 (UTC) Date: Mon, 19 Aug 2019 16:11:00 +0000 (UTC) From: "Allen Wittenauer (Jira)" To: notifications@yetus.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YETUS-905) patch downloads can take wrong path MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YETUS-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16910517#comment-16910517 ] Allen Wittenauer commented on YETUS-905: ---------------------------------------- Uploaded the github and jira JSON data and the response from JIRA. It's pretty clear that the plugin was confused by the ASF's maintenance message, but I'm still confused as to how test-patch ended up there. > patch downloads can take wrong path > ----------------------------------- > > Key: YETUS-905 > URL: https://issues.apache.org/jira/browse/YETUS-905 > Project: Yetus > Issue Type: Bug > Components: Precommit > Affects Versions: 0.11.0 > Reporter: Allen Wittenauer > Priority: Major > Attachments: debug-data.tgz > > > Just had this happen this morning; subsequent run worked: > ``` > WARNING: Found both spotbugs and findbugs. Disabling findbugs. > Modes: Circle_CI Robot ResetRepo UnitTests > Processing: https://github.com/lf-edge/eve/pull/205 > GITHUB PR #205 is being downloaded from > https://api.github.com/repos/lf-edge/eve/pulls/205 > JSON data at Mon Aug 19 08:36:24 UTC 2019 > Patch data at Mon Aug 19 08:36:24 UTC 2019 > Diff data at Mon Aug 19 08:36:24 UTC 2019 > ERROR: https://github.com/lf-edge/eve/pull/205 issue status is not matched with "Patch Available". > ... > Exited with code 1 > ``` > While JIRA is enabled, it's a bit surprising it went down that code path since there is no JIRA info configured for this project. We might need to tighten up how JIRA gets invoked, etc. -- This message was sent by Atlassian Jira (v8.3.2#803003)