LLVM-GCC Back

The LLVM-GCC anonymous mirror should be updated now. Let me know if
this happens again.

-bw

Bill wrote:

The LLVM-GCC anonymous mirror should be updated now. Let me know if
this happens again.

-bw

It's still taking over an hour for rsync to occur.

I can try to see if they will move the rsync to a better time. Unfortunately, I don't have much control over that end of it. Would it be possible to run your nightly script later? :slight_smile:

-bw

Bill Wendling wrote:

I'll ping the guy who's in charge of the sync and ask him when it's done. Right now, the copy to the Apple internal mirror is done at 2AM PDT. From your email, I suspect that the sync is done around 3ish. Though maybe it's somehow dependent upon when I update the mirror??

Unfortunately, because we now have people working on LLVM around the clock (hi Anton! :slight_smile: ), pretty much anytime for the sync is going to be a problem for someone. The good news is that this problem will be obviated in about a month! :slight_smile:

-bw

Bill Wendling wrote:

Jeff Cohen wrote:

Bill Wendling wrote:
  

I'll ping the guy who's in charge of the sync and ask him when it's done. Right now, the copy to the Apple internal mirror is done at 2AM PDT. From your email, I suspect that the sync is done around 3ish. Though maybe it's somehow dependent upon when I update the mirror??

Unfortunately, because we now have people working on LLVM around the clock (hi Anton! :slight_smile: ), pretty much anytime for the sync is going to be a problem for someone. The good news is that this problem will be obviated in about a month! :slight_smile:

-bw
      
I delayed it to 3:40am. We'll see if that's late enough.

The answer is no. It is not late enough. llvm-gcc failed to build as a result (yet again) and the nightly tester did not run.

Jeff Cohen wrote:

Jeff Cohen wrote:
  

Bill Wendling wrote:
  

I'll ping the guy who's in charge of the sync and ask him when it's done. Right now, the copy to the Apple internal mirror is done at 2AM PDT. From your email, I suspect that the sync is done around 3ish. Though maybe it's somehow dependent upon when I update the mirror??

Unfortunately, because we now have people working on LLVM around the clock (hi Anton! :slight_smile: ), pretty much anytime for the sync is going to be a problem for someone. The good news is that this problem will be obviated in about a month! :slight_smile:

-bw
      

I delayed it to 3:40am. We'll see if that's late enough.
    
The answer is no. It is not late enough. llvm-gcc failed to build as a result (yet again) and the nightly tester did not run.

And even if the mirror was promptly updated at 2am, it wouldn't have mattered. The mirror got fatally out of sync with llvm less than an hour later. There are still massive errors building llvm-gcc.

And the Visual Studio build is massively broken too. I don't have time to fix it today.

I think Chris (and I) sent patches to be applied after update. At least,
it worked for me just fine at 4:25am

Reid.

I delayed it to 3:40am. We'll see if that's late enough.

The answer is no. It is not late enough. llvm-gcc failed to build as a
result (yet again) and the nightly tester did not run.

And even if the mirror was promptly updated at 2am, it wouldn't have
mattered. The mirror got fatally out of sync with llvm less than an
hour later. There are still massive errors building llvm-gcc.

Yes, as you are finding out, there is no solution other than to drop the whole "mirror" approach entirely. Luckily, we are planning to do just that! I'm sorry that this is such a pain, but it should be over soon.

And the Visual Studio build is massively broken too. I don't have time
to fix it today.

I'm sorry for that. I will be checking in changes today to remove the bcreader/writer directories, so please wait until that is done to rebuild the project files.

Thanks for the patience Jeff, LLVM 2.0 is almost here - our development process will get better when it does :slight_smile:

-Chris

Jeff Cohen wrote:

And even if the mirror was promptly updated at 2am, it wouldn't have
mattered. The mirror got fatally out of sync with llvm less than an hour later. There are still massive errors building llvm-gcc.
  
My nightly tester still can't build llvm-gcc.

And the Visual Studio build is massively broken too. I don't have time to fix it today.

It is now fixed.

And even if the mirror was promptly updated at 2am, it wouldn't have
mattered. The mirror got fatally out of sync with llvm less than an
hour later. There are still massive errors building llvm-gcc.

My nightly tester still can't build llvm-gcc.

This is not very useful. Please file a PR and provide details on what errors you are getting and what platform. Someone will take a look at it then.

-Tanya

Tanya M. Lattner wrote:

And even if the mirror was promptly updated at 2am, it wouldn't have
mattered. The mirror got fatally out of sync with llvm less than an
hour later. There are still massive errors building llvm-gcc.

My nightly tester still can't build llvm-gcc.

This is not very useful. Please file a PR and provide details on what errors you are getting and what platform. Someone will take a look at it then.

-Tanya

It can't build it because the API keeps changing faster than the mirror can keep up. It would be more useful to keep the API stable, as the freeze is right around the corner, than to file a PR. Or I can simply stop running the nightly tester until the conversion to svn occurs and the mirror is history. In fact, that is what I'll do. It is not worth the hassle.