[jira] [Commented] (YETUS-547) Race condition when executing docker mode and an issue tracker gets updates

["Sean Busbey (JIRA)" <ji...@apache.org>]

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

Sean Busbey commented on YETUS-547:
-----------------------------------

Here's the jira report that appears to just be the later patch mysteriously failing: [ref|https://issues.apache.org/jira/browse/HBASE-18833?focusedCommentId=16170084&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16170084]

Here's the build, which has been pinned for now: [ref|https://builds.apache.org/job/PreCommit-HBASE-Build/8686/]

> Race condition when executing docker mode and an issue tracker gets updates
> ---------------------------------------------------------------------------
>
>                 Key: YETUS-547
>                 URL: https://issues.apache.org/jira/browse/YETUS-547
>             Project: Yetus
>          Issue Type: Bug
>          Components: Test Patch
>    Affects Versions: 0.5.0
>            Reporter: Sean Busbey
>            Priority: Minor
>
> Over in hbase we had a race condition where test patch's docker mode saw two different patches attached to an issue. The first one was used to pick the docker image and then on reexec we checked the issue tracker for a patch for a second time and got a different patch. The two patches were for different branches with different JVM requirements, which gave spurious failures.
> We should pass the patch we already downloaded in to the docker mode reexecution.
> Workaround: wait until a given run has gotten past the second patch finding before updating your issue tracker with a new patch.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)