You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Francois Saint-Jacques (JIRA)" <ji...@apache.org> on 2019/06/28 19:38:00 UTC

[jira] [Resolved] (ARROW-5781) [Archery] Ensure benchmark clone accepts remotes in revision

     [ https://issues.apache.org/jira/browse/ARROW-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francois Saint-Jacques resolved ARROW-5781.
-------------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.14.0

Issue resolved by pull request 4741
[https://github.com/apache/arrow/pull/4741]

> [Archery] Ensure benchmark clone accepts remotes in revision
> ------------------------------------------------------------
>
>                 Key: ARROW-5781
>                 URL: https://issues.apache.org/jira/browse/ARROW-5781
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Developer Tools
>    Affects Versions: 0.13.0
>            Reporter: Francois Saint-Jacques
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 0.14.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Found that ursabot would always compare the PR tip commit with itself via https://github.com/apache/arrow/pull/4739#issuecomment-506819250 . This is due to buildbot github behavior of using a git-reset --hard local that changes the `master` rev to this new state. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)