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

Posted to infrastructure-issues@apache.org by "Geoffrey Corey (JIRA)" <ji...@apache.org> on 2015/09/08 22:38:46 UTC

[jira] [Resolved] (INFRA-9988) Spark GitHub PRs didn't get closed automatically after merge

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

Geoffrey Corey resolved INFRA-9988.
-----------------------------------
    Resolution: Cannot Reproduce

I didn't hear anything helpful from GitHub support (they say it was an issue on our end). We did identify a potential issue with the mirror sync daemon, and it seems that the sync process has been keeping up. On the plus side, we have the mirror sync daemon logs going into our new logging system so we should be able to get some insight if the problem shows up again. I'm going to go ahead and resolve the issue.

> Spark GitHub PRs didn't get closed automatically after merge
> ------------------------------------------------------------
>
>                 Key: INFRA-9988
>                 URL: https://issues.apache.org/jira/browse/INFRA-9988
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>            Reporter: Xiangrui Meng
>            Assignee: Geoffrey Corey
>
> Many recent PR remained open after merge, for example, https://github.com/apache/spark/pull/7367. This might be related to INFRA-9782. Since this issue happens from time to time, it would be nice to grant Spark PMCs (or committers) access to close PRs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)