You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2017/06/26 22:57:00 UTC
[jira] [Updated] (YETUS-485) Yetus run is failing on branch after
rebase/force push
[ https://issues.apache.org/jira/browse/YETUS-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated YETUS-485:
-----------------------------------
Component/s: Test Patch
> Yetus run is failing on branch after rebase/force push
> ------------------------------------------------------
>
> Key: YETUS-485
> URL: https://issues.apache.org/jira/browse/YETUS-485
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Affects Versions: 0.5.0
> Environment: Apache Jenkins build server
> Reporter: Subru Krishnan
> Assignee: Subru Krishnan
> Priority: Critical
> Fix For: 0.5.0
>
> Attachments: YETUS-485.01.patch, YETUS-485.02.patch, YETUS-485.03.patch, YETUS-485.04.patch
>
>
> I rebased YARN-2915 with trunk and did a force push following which all Yetus runs fails as the local enlistment in the jenkins slave is outdated: https://builds.apache.org/job/PreCommit-YARN-Build/14775/console. Looked at it with [~chris.douglas] and [~asuresh]'s help and we decided to directly use the commit hash based on https://github.com/apache/yetus/blob/master/precommit/test-patch.sh#L1356-L1368 but even that didn't work out as yetus does a pull after the checkout: https://builds.apache.org/job/PreCommit-YARN-Build/14800/console.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)