www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Corey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-10730) AsterixDB github mirror out of date
Date Fri, 06 Nov 2015 18:32:10 GMT

    [ https://issues.apache.org/jira/browse/INFRA-10730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994160#comment-14994160

Geoffrey Corey commented on INFRA-10730:

Depends. Was the commit a rather large commit? If so, there is the chance it hit a race condition
where the mirroring daemon was triggered to update before the contents on git-wip-us were
actually updated.

If this happens, there is a self-service way to trigger a new sync, and that is to push another
commit with changes (trivial whitespace change, etc). That should kick the mirroring daemon
to sync the repo. If this doesn't work then a JIRA ticket is appropriate :)

For now I'll trigger a manual sync.

> AsterixDB github mirror out of date
> -----------------------------------
>                 Key: INFRA-10730
>                 URL: https://issues.apache.org/jira/browse/INFRA-10730
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>            Reporter: Chris Hillery
>            Assignee: Geoffrey Corey
> Tip of AsterixDB repo is 55f26c7: https://git-wip-us.apache.org/repos/asf?p=incubator-asterixdb.git
> But tip of GitHub mirror is 391f09e: https://github.com/apache/incubator-asterixdb
> Newer commit was pushed 10 hours ago - should we normally expect the GitHub mirror to
be running that far behind?

This message was sent by Atlassian JIRA

View raw message