systemml-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deron Eriksson <deroneriks...@gmail.com>
Subject Re: SystemML github mirror is behind one commit
Date Fri, 11 Dec 2015 18:58:23 GMT
Thank you Geoffrey for the rapid response and the useful information! It is
greatly appreciated.

Deron


On Fri, Dec 11, 2015 at 10:54 AM, Geoffrey Corey <coreyg@apache.org> wrote:

> Looks like the git mirror is having some issues and locking up when
> syncing some of the svn->git mirrors. I have triggered a manual sync now,
> and am working on fixing up the mirror.
>
> In the future, you can try a sefl-service fix by commiting something like
> a whitespace change (has to contain a change of some sort), and if that
> doesn't work, you should open a JIRA, as INFRA gets a lot of emails and
> there's a chance it will unintentionally get drowned in the noise.
>
> On Fri, Dec 11, 2015 at 10:42 AM, Deron Eriksson <deroneriksson@gmail.com>
> wrote:
>
>> Hi,
>>
>> The SystemML GitHub mirror repo is missing the latest commit again
>> compared with the Apache SystemML git repo. Would it be possible for
>> someone to look at this? Please let me know if I should create a JIRA.
>>
>> Thank you
>> Deron
>>
>> On Sun, Dec 6, 2015 at 4:31 AM, Daniel Gruno <humbedooh@apache.org>
>> wrote:
>>
>>> On 12/06/2015 05:36 AM, Luciano Resende wrote:
>>> > Looks like the SystemML github mirror is missing one commit compared to
>>> > Apache SystemML git repository.
>>> >
>>> > git log --oneline master..apache/master
>>> > 41d9d2c Remove copyrights from license, add license where needed
>>> >
>>> > What's the best way to fix this issue ? Should I create a JIRA ?
>>> >
>>> > Thank you.
>>> >
>>> > --
>>> > Luciano Resende
>>> > http://people.apache.org/~lresende
>>> > http://twitter.com/lresende1975
>>> > http://lresende.blogspot.com/
>>>
>>> Hi Luciano et al,
>>> I've done a manual update of it now. This was likely missed because of
>>> the size of the commit. When a commit gets pushed, the sync process
>>> waits N seconds, then fetches the updates. If all the updates haven't
>>> been fully processed yet by the git backend, not all updates are fetched
>>> (and how is the poor system supposed to know that), so it happily pushes
>>> whatever it gets on to GitHub. I suppose we could increase the waiting
>>> period and see if that helps.
>>>
>>> With regards,
>>> Daniel.
>>>
>>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message