[llvm-commits] llvm-gcc mirror update delayed again

[Bill Wendling]

On Apr 29, 2007, at 7:24 AM, Reid Spencer wrote:

> On Sun, 29 Apr 2007 07:11:45 -0700
>  Jeff Cohen <jeffc at jolt-lang.org> wrote:
>> It happened again last night.  According to the log:
>>
>> --------------------------------------------------------------------- 
>> ---
>> r319 | bwendlin | 2007-04-29 02:04:05 -0700 (Sun, 29 Apr 2007) | 1  
>> line
>>
>> auto-merge 2007-04-29T02:00:00-0700
>> --------------------------------------------------------------------- 
>> ---
>>
>> it updated at 2am.  But my nightly tester at 3am did not pull in 319,
>> only 318 (which it failed to pull in the previous night).  But  
>> updating
>> now pulls in 319.
>
> As I suspected, I think those times are bogus :)
>
>>
>> So when is the mirror updated? If not 2am, why does the log show 2am?
>> If it is 2am, then how does an update an hour later fail to see it?
>
> Bill needs to answer those questions.
>
I'll need to check, but the process seems to be two-step (I inherited  
it from Jim L., so I'm not up on all of the fine details). My  
understanding is that there's a merge script that's run at 2AM every  
night. That's why you get the "auto-merge" messages with that  
timestamp. It's from there that another script (which I don't  
control) does an rsync with the external tree. That one might be  
coming later in the day.

This is yet one more reason why going to the single SVN repository  
will be *so* welcome. We won't have these types of errors again.

>> And
>> why does there have to be a mirror in the first place?  Why can't  
>> you do
>> your commits directly to a publicly accessible repository?  What  
>> benefit
>> is there to keeping the code under wraps for less than 24 hours?
>
There is no benefit. In fact, it's a needless pain in the ass. :-)

> Jeff, we all suffer this frustration. If we could change it, it  
> would be better by now.  It is the way it is because of how Apple  
> has organized their internal repository. llvm-gcc is comingled with  
> Apple GCC and that repository isn't accessible outside Apple.  
> Consequently, the mirror allows llvm-gcc to be accessible by the  
> community without providing access to the rest of Apple GCC (or  
> something like that, I'm vague on the details).
>
> We would have a fully commitable llvm-gcc repository under  
> Subversion by now if we were cut over, but we're not. Because  
> there's a lot going on in the community right now, we've put off  
> the SVN migration until June. So, a few more weeks of patience and  
> things should get much better in this regard.
>
I agree. It's a growing pain. Please be patient. An alternative is to  
take the SVN messages posted here and update your llvm-gcc repository  
yourself. In truth, the number of changes to the llvm-gcc rep. aren't  
nearly the number that goes into LLVM proper, so the amount of pain  
it takes to merge in the patches by hand isn't as great. And it would  
only be for another month. :-)

-bw