[ https://issues.apache.org/jira/browse/YETUS-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16910519#comment-16910519 ]
Allen Wittenauer commented on YETUS-905: ---------------------------------------- It's worth nothing that the input.diff and input.patch files were present. > 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)