yetus-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yetus QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YETUS-485) Yetus run is failing on branch after rebase/force push
Date Wed, 08 Mar 2017 01:59:37 GMT

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

Yetus QA commented on YETUS-485:
--------------------------------

(!) A patch to the testing environment has been detected. 
Re-executing against the patched versions to perform further tests. 
The console is at https://builds.apache.org/job/PreCommit-YETUS-Build/543/console in case
of problems.


> 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
>    Affects Versions: 0.5.0
>         Environment: Apache Jenkins build server
>            Reporter: Subru Krishnan
>            Assignee: Subru Krishnan
>            Priority: Critical
>         Attachments: YETUS-485.01.patch, YETUS-485.02.patch, YETUS-485.03.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.3.15#6346)

Mime
View raw message